[openstack-dev] [all][release] Release countdown for week R-4, Mar 7 - 11
skraynev at mirantis.com
Wed Mar 9 08:08:32 UTC 2016
I have one question related with last item: "Release actions".
Who will prepare patches for Reno and for updating .gitreview?
Should it be done by related project team or it will be done by someone else?
On 5 March 2016 at 02:01, Doug Hellmann <doug at doughellmann.com> wrote:
> The Mitaka 3 milestone has passed, and we're on our way to preparing
> release candidates. See Thierry's email  for details about the
> artifacts produced for the milestone.
>  http://lists.openstack.org/pipermail/openstack-announce/2016-March/001002.html
> Project teams should be concentrating on finishing work for which
> a feature freeze exception (FFE) was granted, and fixing release-critical
> bugs before preparing the release candidates during week R-3. Any
> FFE work not completed this week should be postponed to the next
> General Notes
> The global requirements list is frozen. If you need to change a
> dependency, for example to include a bug fix in one of our libraries
> or an upstream library, please provide enough detail in the change
> request to allow the requirements review team to evaluate the change.
> User-facing strings are frozen to allow the translation team time
> to finish their work.
> Release Actions
> The stable/mitaka branches for libraries will be created early
> during R-4. After the branch is created, a patch will be submitted
> to update the .gitreview file. If the project uses reno, another
> patch will be submitted on master to add a mitaka-specific page to
> the reno build. Please watch for those patches and prioritize
> reviewing them.
> Important Dates
> RC Target Week: R-3, Mar 14-18
> Mitaka release schedule: http://releases.openstack.org/mitaka/schedule.html
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev