[openstack-dev] [horizon] Pike-3, Feature Freeze, and next steps
robert.cresswell at outlook.com
Fri Jul 28 10:25:19 UTC 2017
We tagged Horizons Pike-3 milestone about 12 hours, so I wanted to quickly run through the next steps for the release. At this point, we are in "Feature Freeze" and also "Soft String Freeze".
- Feature Freeze - No new features (blueprints or wishlist bugs) can be merged without the PTLs approval. We do this so that we can spend the next few weeks focusing on finding and fixing bugs in the existing content, to create a stable release.
- Soft String Freeze: No user-facing strings should be altered and new string additions in general are discouraged, although not blocked entirely. This is to give the translation teams some time to start working through the various string additions or changes this cycle. For example, when fixing bugs, try to reuse the existing error messages rather than alter them.
In 2 weeks time, around the 10th of August, we will tag RC1 (Release Candidate 1) and move to "Hard String Freeze". At this point, all new strings are blocked, while the translation teams do their work. RC1 will become the new stable branch ("stable/pike" in this instance) and master branch will open for Queens-1.
Any bug fixes for further Pike RC's must then be merged to master and backported, as with standard stable policy. Horizon always has an RC2 for translation merges. If you'd like to learn more about the deadlines described here, https://releases.openstack.org/pike/schedule.html and https://docs.openstack.org/project-team-guide/release-management.html are useful references.
If you have any questions, please get in touch by replying here or pinging me on IRC (robcresswell) in the #openstack-horizon channel.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev