Zuul Branch Naming for Post Release Support

Once a release such as Ardana Cloud-8 has shipped we need created a branch in zuul for the ardana/* repos. This will a provide a place for any bug fixes for the current released product to be done after the master branch as moved on to the next release. The requirements on the branch are the following:

1. Can be created from master so long as no changes for the next release has been made to master.
2. Normally created soon after MU-1 is final, to minimize the need for cherry-picking changes
3. Name should have some logical relationship to its parent. So, support-0618 would be out, as would Frodo, Balbo, Bilbo and Samwise.
4. Name should not contain references to either the product or the release, since that might confuse the community at large.
5. All support branches are created as stable/xxxxx to denoted that they represent code that has been released vs. code that is under development.

Applying these rules to the Cloud-8 release, we have ruled out:

• stable/SOC8 (contains product name)
• stable/Cloud8 (contains product name)
• stable/8 (don't like single digit branches)

Since the Ardana Cloud 8 release is OpenStack Pike based and all of the code in the ardana/* repos is the plumbing needed for the Pike release; it makes sense to have the support branch be stable/pike. This is also good because it follows the convention set forth by OpenStack. Carrying this forward we would have:

• SOC8/Ardana Cloud8 support branch stable/pike
• SOC9/Ardana Cloud9 support branch stable/rocky
• SOC10/Ardana Cloud10 support branch stable/t??????