-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
As part of our effort to streamline branch cut process we want to be able to add new releases and import data prior to branch cut. Currently the only thing preventing this is that the Sippy default release is that most recent release.
- We instead want the default to be the first non-ga dev branch.
- Sippy should show the new release, just not default to it
Once we do this we can update our Branch Cut procedure to allow adding the new release prior to branch cut