Open Stack

Hi!

Unfortunately, it seems that we've discovered a critical issue in one of our 
libs (sushy) right after branching :( What's the procedure for emergency fixes 
to stable/queens right now?

On 01/19/2018 10:15 PM, Sean McGinnis wrote:
> Happy Friday all.
> 
> Now that we are past the non-client lib freeze, we will need to have
> stable/queens branches for those libs. For all libraries that did not miss the
> freeze, I will be proposing the patches to get those stable branches created.
> 
> This should have been enforced as part of the last deliverable request, but I
> don't think we had quite everything in place for branch creation. Going forward
> as we do the client library releases and then the service releases, please make
> sure your patch requesting the release includes creating the stable/queens
> branching.
> 
> If there is any reason for me to hold off on this for a library your team
> manages, please let me know ASAP.
> 
> 
> Upcoming service project branching
> ==================================
> 
> I mentioned this in the countdown email, but to increase the odds that someone
> actually sees it - if your project follows the cycle-with-milestones release
> model, please check membership of your $project-release group. The members of
> the group can be found by filtering for the group here:
> 
> https://review.openstack.org/#/admin/groups/
> 
> This group should be limited to those aware of the restrictions as we wrap up
> the end of the cycle to make sure only release critical things are allowed to
> be merged into stable/queens as we finalize things for the final release.
> 
> As always, just let me know if there are any questions.
> 
> --
> Sean McGinnis (smcginnis)
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>