Considering changing the way auto-deploy names it's branches
In the 12.4 release process:
We created the branch on the 18th as we desired, but due to milestone scheduling, this caused the branch to be named
12-5-...
. Subsequently each time our tooling left a message, it included the verbiage related to12.5
which is incorrect. This spawned a large amount of confusion as many issues were then tagged with the missed deliverable label, and engineers started to ask questions.
Based on feedback from others we have a few options:
- Check for the latest stable branch name
- Derive the name from that branch and use it for auto-deploy
- Automate creation of stable branches as mentioned
- If we base it off of a CI variable we will need to manually or automatically update it immediately after we create the final auto-deploy branch on the 18th (or whenever that is)
- If we base it off of
VERSION
we will need to manually update it as well, or have something automated that does - Remove MAJOR.MINOR from the name of the branch and tag for auto-deploys
Utilize this issue to discuss the above options and make the appropriate changes where necessary.