<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">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?</div> <br> <div id="bloop_sign_1459281894922173952" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev</div><div style="font-family:helvetica,arial;font-size:13px">Murano Team</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div> <br><p class="airmail_on">On 29 March 2016 at 19:46:08, Doug Hellmann (<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>During the Mitaka cycle, the release team worked on automation for
<br>tagging and documenting releases [1]. For the first phase, we focused
<br>on official teams with the release:managed tag for their deliverables,
<br>to keep the number of projects manageable as we built out the tools
<br>and processes we needed. That created a bit of confusion as official
<br>projects still had to submit openstack/releases changes in order
<br>to appear on the releases.openstack.org website.
<br>
<br>For the second phase during the Newton cycle, we are prepared to
<br>expand the use of automation to all deliverables for all official
<br>projects. As part of this shift, we will be updating the Gerrit
<br>ACLs for projects to ensure that the release team can handle the
<br>releases and branching. These updates will remove tagging and
<br>branching rights for anyone not on the central release management
<br>team. Instead of tagging releases and then recording them in the
<br>releases repository after the tag is applied, all official teams
<br>can now use the releases repo to request new releases. We will be
<br>reviewing version numbers in all tag requests to ensure SemVer is
<br>followed, and we won't release libraries late in the week, but we
<br>will process releases regularly so there is no reason this change
<br>should have a significant impact on your ability to release frequently.
<br>
<br>If you're not familiar with the current release process, please
<br>review the README.rst file in the openstack/releases repository.
<br>Follow up here on the mailing list or in #openstack-release if you
<br>have questions.
<br>
<br>The project-config change to update ACLs and correct issues with
<br>the build job definitions for official projects is
<br>https://review.openstack.org/298866
<br>
<br>Doug
<br>
<br>[1] http://specs.openstack.org/openstack-infra/infra-specs/specs/centralize-release-tagging.html
<br>
<br>__________________________________________________________________________
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<br></div></div></span></blockquote></body></html>