Proposal: A formalized "new build" framework

[adamfarley]

Summary A framework to cover the addition of new builds to Adopt jenkins.

Details To include an agreement on the following:

• How such a build should be proposed, including:
  • Minimum data requirements
  • Location of proposal issue
  • Template?
• The prerequisites for approval, including:
  • A list of details to be approved (platforms, versions, VMs, frequency of build, testing, total time cost by platform, POCs, implementation champion, releases if any, etc)
  • The minimum amount of testing for the build to be declared "good", or published at all each day/week.
  • Method of approval (number of approvers, collective TSC approval, etc)
• The follow-up, such as:
  • When will we review the build for usefulness?
  • Who will monitor these builds for quality, and how?

Discussion encouraged.

[aahlenst]

Context: This popped up while discussing the addition of Amber builds. The objective is to ensure that we can handle additional builds (no matter whether they are preview builds or some other kind of builds), that it's clear what we expect and others can expect from us.

[sxa]

At the moment I'd avoid adding anythig to the production pipelines until we have determined the rules of engagement with the move to Adoptium.

[smlambert]

Related: https://github.com/AdoptOpenJDK/TSC/issues/186

[karianna]

temurin-build docs cover this.