<div dir="ltr">Dmitry,<div>+2 on the approach, thanks for very clear explanation. Let's put this into wiki and accept it into action.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 1:29 PM, Dmitry Pyzhov <span dir="ltr"><<a href="mailto:dpyzhov@mirantis.com" target="_blank">dpyzhov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 2:33 AM, Dmitry Borodaenko <span dir="ltr"><<a href="mailto:dborodaenko@mirantis.com" target="_blank">dborodaenko@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When you create a bug against a project (in our case, fuel) in<br>
Launchpad, it is always initially targeted at the default release<br>
series (currently, 5.1.x). On the bug summary, that isn't explicitly<br>
stated and shows as being targeted to the project in general (Fuel for<br>
OpenStack). As you add more release series to a bug, these will be<br>
listed under release series name (e.g. 5.0.x).<br>
<br>
Unfortunately, Launchpad doesn't limit the list of milestones you can<br>
target to the targeted release series, so it will happily allow you to<br>
target a bug at 4.1.x release series and set milestone in that series<br>
to 5.1.<br>
<br>
A less obvious inconsistency is when a bug is found in a stable<br>
release series like 5.0.x: it seems natural to target it to milestone<br>
like 5.0.1 and be done with it. The problem with that approach is that<br>
there's no way to reflect whether this bug is relevant for current<br>
release series (5.1.x) and if it is, to track status of the fix<br>
separately in current and stable release series.<br>
<br>
Therefore, when triaging new bugs in stable versions of Fuel or<br>
Mirantis OpenStack, please set the milestone to the next release in<br>
the current release focus (5.1.x), and target to the series it was<br>
found in separately. If there are more recent stable release series,<br>
target those as well.<br>
<br>
Example: a bug is found in 4.1.1. Set primary milestone to 5.1 (as<br>
long as current release focus is 5.1.x and 5.1 is the next milestone<br>
in that series), target 2 more release series: 4.1.x and 5.0.x, set<br>
milestones for those to 4.1.2 and 5.0.1 respectively.<br>
<br>
If there is reason to believe that the bug does not apply to some of<br>
the targeted release series, explain that in the commit and mark the<br>
bug Invalid for that release series. If the bug is present in a series<br>
but cannot be addressed there (e.g. priority is not high enough to do<br>
a backport), mark it Won't Fix for that series.<br>
<br>
If there are no objections to this approach, I'll put it in Fuel wiki.<br>
<br>
Thanks,<br>
-DmitryB<br>
<span><font color="#888888"><br>
--<br>
Dmitry Borodaenko<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div>
</div>