Discussion: naming convention for buildReference

[zdtsw]

We should define what the git tag should be formed when we set it on the and used in the official release for input buildReference

Since they will be used for reproducible build, unless we decided to use SHA instead of tag in the build, we should never move tags around. create new one if needed

Suggestion:v<YY>.<MM>.01 e.g for 2022 Oct CPU release, v2022.10.01 if any hot bug fix, we can create v2022.10.02 and so on.

DoD:

• what the name should be for tag
• be clear the process: who will apply such tag and when it should be done pre-release
• update https://github.com/adoptium/temurin-build/blob/master/RELEASING.md#steps-for-every-version

Ref: https://github.com/adoptium/ci-jenkins-pipelines/issues/495

[zdtsw]

we will use below format as a start:

for trail test: vYYYY.MM.beforereleasetest for official tag: vYYYY.MM.0X (X starts from 1 and can be increased for patch build)