Discussion: what targetConfiguration should be put into prototype pipeline

[zdtsw]

We are adding support for generate prototype pipeline and jobs.
We want to be able to have unstable/not-ready-yet target in the prototype pipeline till we have confidence.

The difference of nightly VS prototype is:

1. nightly pipeline runs 2-3 times a week and use "Nightly" as releaseType
2. prototype pipeline can have the same or a different timer trigger than nightly(this is up to config) and use "Nightly not publish" as releaseType => wont be able to download build result from Github repo as pre-release
   for the current implementation: both of them share the same testsuite (i.e if nightly runs "default" then prototype runs "default" as well)

The difference of weekly VS weekly-prototype is:

1. weekly runs during the weekend, it calls nightly pipeline but set "Release" as releaseType. it uses weeklyDefault for Aqatest and should trigger JCK
2. weekly-prototype runs during the weekend(up to config), it calls prototype pipeline, but set "Nightly not publish" as releaseType. it uses weeklyDefault for Aqatest but should not trigger JCK

The goal for this issue is to identify which targets should be put into prototype.
Some to consider:

1. should non-temurin variants be in the nightly or prototype?
2. should target that we do not officially release be in the nightly or prototype?
3. should new platform/OS be in the nightly or prototype?
4. might be something more

Ref: #473

[gdams]

Here's my thoughts:

should non-temurin variants be in the nightly or prototype?

yes - and we should make a point to clear up the old jobs to tidy up the jobs folder

should target that we do not officially release be in the nightly or prototype?

if we don't release them (e.g they are experimental) they should be in prototype

should new platform/OS be in the nightly or prototype?

It should likely start out in prototype until we've proven that the build is stable and triaged any test failures. At that point we can promote it to the main pipeline with PMC approval

[smlambert]

Anything we do not release should go in the prototype incubator nonrelease experimental evaluation pipeline, since we are evaluating them for various reasons (other distros to aid in triage and improve automation / train models) and new platforms for stabilization.

[andrew-m-leonard]

I think we've setup what we already need for evaluation