Migrate TensorFlow community-builds table

[angerson]

This PR pulls the Community Builds table from tensorflow/tensorflow into SIG Build, and rearranges it for easier maintenance. Specifically:

• I added explicit owners + contact columns
• I alphabetized the list
• I shortened a couple long names

Before this gets merged, I need to get ~90% confirmation that the owners are correct, broken links will be fixed, and that the way this is laid out is OK with everyone. In a comment below I'll tag everyone to ask specific questions.

Check the "build-table" branch linked above to see the new page in action.

[angerson]

FYI @lamberta @wolffg

• @deven-amd Can you confirm the AMD builds are up-to-date and the owners table is correct?
  • The Stable Release v1 link was last built over a year ago and the v2 link 404s.
  • Can we split into two rows so we get badges for 1.x and 2.x?
• @wdirons @jayfurmanek Can you confirm the IBM builds are up-to-date and the owners table is correct?
  • The PPC Nightly builds are disabled and didn't pass often. Should we remove them? WIP, kept
  • The PPC v2 build hasn't run since TF 2.2, should it be removed? WIP, kept
  • Can we split remaining builds into multiple rows so we get badges for 1.x and 2.x? Done
• @gaurides @claynerobison Can you confirm the Intel builds are up-to-date and the owners table is correct?
  • The release artifacts look like they work, but the build status badge links to the badge itself.
  • I shortened the name to just Intel OneDNN because it extended the column a lot. Is that OK?
• @hrw @paulisaacs-linaro Can you confirm the Linaro builds are up-to-date and the owners table is correct?
  • All the links go to the place you can download artifacts, which should be good!
• @bzhaoopenstack Can you confirm the OpenLab builds are up-to-date and the owners table is correct?
  • Stable last ran in August, for TF 2.1. Is that right?
• @sub-mod Can you tell me how to fix the RedHat builds? The links are broken. Is the owners table correct?

[lamberta]

Thanks, @angerson !
Might be worth adding a sentence and link here in the build from source guide. (We already link to SIG Build in the toc but could help funnel users who end up on that page through search.)

[sub-mod]

@angerson will take a look next week. the CI cluster needs a reboot.

[angerson]

Might be worth adding a sentence and link here in the build from source guide

Yeah, good idea. Once this PR is ready to go I'll prep the docs changes and do them at the same time.

[hrw]

@angerson links to Linaro builds are pointing into proper places. Also contact persons match.

We are at 1.5.15 / 2.4.1 / git HEAD (2.6.0).

[jayfurmanek]

Hi Austin,

>The PPC Nightly builds are disabled and didn't pass often. Should we remove them? >The PPC v2 build hasn't run since TF 2.2, should it be removed?

For the ppc builds, we had a problem in Eigen where an optimization was added for ppc64le, but it broke the integration with Tensorflow, so the daily was disabled in the Jenkins. I don't want to remove them.   The issue was recently resolved: tensorflow/tensorflow#44626   The PR builds are still disabled on the Jenkins, however, because we need to get the build image updated. Local builds work.

>Can we split remaining builds into multiple rows so we get badges for 1.x and 2.x?

yeah - I think that's fine. The 1.x builds were unaffected by the issue above and still work ok.

[angerson]

Thanks @jayfurmanek and @hrw. Can you also comment on the "Support" sections on the ownership table? I figure we may want different policies for users with "the build links are broken" issues (handled by the owners) vs. "the artifacts don't work for my machine" issues. So that section could e.g. be "send an email to [user]" or "file ticket to [tracker]". What do you think?

[deven-amd]

@angerson

@deven-amd Can you confirm the AMD builds are up-to-date and the owners table is correct?

The AMD nightly build pointer is up-to-date (build is failing, but should get back to passing once all outstanding PRs are merged) and the owners table is accurate.

The Stable Release v1 link was last built over a year ago and the v2 link 404s.

The Stable Releases links for both v1 and v2 are stale, and need to be refreshed. I will follow up on this next week.

Can we split into two rows so we get badges for 1.x and 2.x?

yes please. I can do that when I submit the PR to update the Stable Release links next week.

[angerson]

In the interest of unblocking, I'll merge this as-is, update the main README, and file an issue here with the remaining things to do.