<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 04/24/2013 06:03 PM, John Griffith wrote:
<blockquote
cite="mid:CA+qL3LUOZk=vmgh9Kc6QMWK93jU9_GGx-Ttwwi_KM+N0ekY0Jg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Apr 24, 2013 at 8:30 AM,
Vishvananda Ishaya <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">I can't say for sure if other projects follow
this but generally I tag each bug report with
grizzly-backport-potential. When I go to do the backport
I remove the tag and target it to the grizzly series and
propose it. If the back port itself is tricky, I
sometimes ask the original author to do it.</p>
<p dir="ltr">Vish</p>
</blockquote>
<div><br>
</div>
<div style="">I've been following the process Vish described
in Cinder as well.</div>
</div>
</div>
</div>
</blockquote>
<br>
In Quantum I do practically the same. I only remove the tag when the
patch has been approved (makes it easier to track).<br>
<br>
<blockquote
cite="mid:CA+qL3LUOZk=vmgh9Kc6QMWK93jU9_GGx-Ttwwi_KM+N0ekY0Jg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div style=""> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">
<div class="gmail_quote">On Apr 24, 2013 12:40 AM,
"Adam Gandelman" <<a moz-do-not-send="true"
href="mailto:adamg@canonical.com" target="_blank">adamg@canonical.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 04/22/2013 02:57 PM, Alan Pevec wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
So there was a session, notes are in etherpad
[1]<br>
<br>
Adam Gandelman (adam_g on irc) and Alan Pevec
(apevec on irc) will<br>
take over, in turns, managing stable/grizzly
releases from markmc.<br>
<br>
Adam, please join this list<br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a><br>
I've added you to openstack-stable-maint in
Gerrit, welcome to the team!<br>
<br>
First stable/grizzly release 2013.1.1 is planned
for May 9 - early<br>
release to pick up critical Grizzly fixes as
suggested by Daviey.<br>
That puts stable freeze date on May 2, which is
already next week!<br>
<br>
There are 28 open bugs tagged
grizzly-backport-potential [2] out of<br>
that 14 have a patch (status In progress).<br>
</blockquote>
<br>
<br>
Hi Alan-<br>
<br>
Thanks for the follow up and adding me to the
team. I've been looking through the bug and patch
queues and had a couple of questions:<br>
<br>
- The LP search you linked to only contains bugs
with open tasks. Adding 'Fix Committed' [1] shows
many more that are tagged, fixed in project's
master but not proposed to stable/grizzly. I
assume we should also make sure these get tracked
as well? I see a few relatively small patches
that seem suitable for stable backport, eg [2]<br>
<br>
- Should core-devs/PTLs be nominating bugs as
affecting Grizzly before someone else proposes a
backport? Or are we only looking for tags? I
couldn't grok the importance of bug tasks /
nominations from the wiki. Based on experiences
elsewhere in the LP/Ubuntu world, I had assumed a
Confirmed bug nomination against Grizzly is
confirmation from PTL/core-dev that the fix is
suitable for backporting to stable.<br>
<br>
Thanks again,<br>
Adam<br>
<br>
[1] <a moz-do-not-send="true"
href="https://bugs.launchpad.net/bugs/+bugs?field.status%3Alist=NEW&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=FIXCOMMITTED&field.tag=grizzly-backport-potential&field.tags_combinator=ANY&search=Search&orderby=-id&start=0"
target="_blank">https://bugs.launchpad.net/bugs/+bugs?field.status%3Alist=NEW&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=FIXCOMMITTED&field.tag=grizzly-backport-potential&field.tags_combinator=ANY&search=Search&orderby=-id&start=0</a><br>
<br>
[2] <a moz-do-not-send="true"
href="https://bugs.launchpad.net/keystone/+bug/1125637"
target="_blank">https://bugs.launchpad.net/keystone/+bug/1125637</a><br>
<br>
<br>
_______________________________________________<br>
Openstack-stable-maint mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openstack-stable-maint@lists.openstack.org"
target="_blank">Openstack-stable-maint@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a><br>
</blockquote>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Openstack-stable-maint mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openstack-stable-maint@lists.openstack.org">Openstack-stable-maint@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openstack-stable-maint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openstack-stable-maint@lists.openstack.org">Openstack-stable-maint@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a>
</pre>
</blockquote>
<br>
</body>
</html>