<html><body><p>So it's only for this time around (Mitaka-1) that I'll have to tag bugs as fix-released, because the release automation will just leave a comment?<br><br>Going forward, the bugs will be automatically marked as fix-released, so the automation won't change their states when we release?<br><br>Thanks,<br><br>Steve Martinelli<br>OpenStack Keystone Project Team Lead<br><br><img width="16" height="16" src="cid:1__=8FBBF595DFE808598f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Doug Hellmann ---2015/11/23 05:00:24 PM---As part of completing the release automation work and depre"><font color="#424282">Doug Hellmann ---2015/11/23 05:00:24 PM---As part of completing the release automation work and deprecating our use of Launchpad for release c</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Doug Hellmann <doug@doughellmann.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">openstack-dev <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">2015/11/23 05:00 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[openstack-dev] [release] process change for closing bugs when patches merge</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>As part of completing the release automation work and deprecating our<br>use of Launchpad for release content tracking, we also want make some<br>changes to the way patches associated with bugs are handled.<br><br>Right now, when a patch with Closes-Bug in the commit message merges,<br>the bug status is updated to "Fix Committed" to indicate that the change<br>is in git, but not a formal release, and we rely on the release tools to<br>update the bug status to "Fix Released" when the release is made. This<br>is one of the most error prone areas of the release process, due to<br>Launchpad service timeouts and other similar issues. The fact that we<br>cannot reliably automate this step is the main reason we want to stop<br>using Launchpad's release content tracking capabilities in the first<br>place.<br><br>To make the release automation reliable, we are going to change the<br>release scripts to comment on bugs, but not update their status, when a<br>release is cut. Unfortunately, that leaves the bugs with "Fix Committed"<br>status, which is still considered "open" and so those bugs clutter up<br>the list of bugs for folks who are looking for ways to help. So, we<br>would like to change the default behavior of our CI and review system so<br>that when a patch with Closes-Bug in the commit message merges the bug<br>status is updated to "Fix Released" instead of "Fix Committed".<br><br>We already have quite a few projects set up this way, using the<br>direct-release option to jeepyb (configured in the gerrit settings in<br>the project-config repository). I'm proposing that we change jeepyb's<br>behavior, rather than applying that flag to all of our projects. We will<br>also add a 'delay-release' flag to jeepyb for projects that want to<br>revert to the old behavior.<br><br>Please let me know if this change would represent a significant<br>regression to your project's workflow.<br><br>Doug<br><br>The infra spec related to this work is: </tt><tt><a href="https://review.openstack.org/#/c/245907/">https://review.openstack.org/#/c/245907/</a></tt><tt><br>The jeepyb change is: </tt><tt><a href="https://review.openstack.org/248922">https://review.openstack.org/248922</a></tt><tt><br>The project-config change to remove the direct-release option from<br>projects: </tt><tt><a href="https://review.openstack.org/#/c/248923">https://review.openstack.org/#/c/248923</a></tt><tt><br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br><br></tt><br><br><BR>
</body></html>