Open Stack

The tagging ACL changes have merged: https://review.openstack.org/#/c/298866/

Doug

> On Mar 29, 2016, at 4:59 PM, Davanum Srinivas <davanum at gmail.com> wrote:
> 
> Kirill,
> 
> This is prep for Newton. So definitely not rocking the boat when we
> have a week left.
> 
> -- Dims
> 
> On Tue, Mar 29, 2016 at 4:08 PM, Kirill Zaitsev <kzaitsev at mirantis.com> wrote:
>> My immediate question is — when would this be merged? Is it a good idea to
>> alter this during the final RC week and before mitaka release, rather than
>> implement this change early in the Newton cycle and let people release their
>> final release the old way?
>> 
>> --
>> Kirill Zaitsev
>> Murano Team
>> Software Engineer
>> Mirantis, Inc
>> 
>> On 29 March 2016 at 19:46:08, Doug Hellmann (doug at doughellmann.com) wrote:
>> 
>> During the Mitaka cycle, the release team worked on automation for
>> tagging and documenting releases [1]. For the first phase, we focused
>> on official teams with the release:managed tag for their deliverables,
>> to keep the number of projects manageable as we built out the tools
>> and processes we needed. That created a bit of confusion as official
>> projects still had to submit openstack/releases changes in order
>> to appear on the releases.openstack.org website.
>> 
>> For the second phase during the Newton cycle, we are prepared to
>> expand the use of automation to all deliverables for all official
>> projects. As part of this shift, we will be updating the Gerrit
>> ACLs for projects to ensure that the release team can handle the
>> releases and branching. These updates will remove tagging and
>> branching rights for anyone not on the central release management
>> team. Instead of tagging releases and then recording them in the
>> releases repository after the tag is applied, all official teams
>> can now use the releases repo to request new releases. We will be
>> reviewing version numbers in all tag requests to ensure SemVer is
>> followed, and we won't release libraries late in the week, but we
>> will process releases regularly so there is no reason this change
>> should have a significant impact on your ability to release frequently.
>> 
>> If you're not familiar with the current release process, please
>> review the README.rst file in the openstack/releases repository.
>> Follow up here on the mailing list or in #openstack-release if you
>> have questions.
>> 
>> The project-config change to update ACLs and correct issues with
>> the build job definitions for official projects is
>> https://review.openstack.org/298866
>> 
>> Doug
>> 
>> [1]
>> http://specs.openstack.org/openstack-infra/infra-specs/specs/centralize-release-tagging.html
>> 
>> __________________________________________________________________________
>> 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
>> 
>> 
>> __________________________________________________________________________
>> 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
>> 
> 
> 
> 
> -- 
> Davanum Srinivas :: https://twitter.com/dims