<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 October 2017 at 10:12, Raghavendra Talur <span dir="ltr"><<a href="mailto:rtalur@redhat.com" target="_blank">rtalur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br>
> Hi,<br>
><br>
> Recently I was in some conversations that mentioned having to hunt for the<br>
> mail that announced the blocker bug for a release, when there is a need to<br>
> mark a bug as a blocker for that release.<br>
><br>
> This need not be done as here is the shortcut (if you did not know) on how<br>
> to find the blocker,<br>
><br>
> Use this URL:<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-</a><<wbr>VERSION><br>
><br>
> Replacing <VERSION> with the version for which you are attempting to find<br>
> the blocker bug for.<br>
><br>
> Example:<br>
> - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.6" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>10.6</a><br>
> - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.7" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>10.7</a><br>
> - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.2" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>12.2</a><br>
><br>
> Some FAQs:<br>
><br>
> - When is the blocker bug created?<br>
><br>
> Blocker bugs are created post branching a release, so if you went around<br>
> hunting for the 3.13.0 blocker today, it does not exist.<br>
><br>
> Blocker bugs for minor releases are created post closing the prior minor<br>
> release, and migrating any blockers that did not make it in the prior<br>
> release to the next minor release blocker (this is only(?) possible as a bug<br>
> maybe marked as blocking a release post tagging the release and before<br>
> actually announcing the release).<br>
><br>
> - When to mark the blocker bug as dependent on another bug:<br>
><br>
> Blockers are meant to track *just* blockers for a major or minor release,<br>
> not all bugs that are a part of the release. Hence when a bug is actually a<br>
> blocker for the release, only then should the tracker be made dependent on<br>
> that.<br>
<br>
</div></div>I have used it a little differently. On the day of release, I add all<br>
the bugs that are fixed in a release in "depends on" list of the<br>
blocker bug. Essentially, I used it as a tracker bug than a blocker<br>
bug.<br>
<br>
Wouldn't it be easier that every bug that one wants to get fixed in<br>
next minor release is added to the tracker bug and is removed and<br>
moved to next release if it did not make it? It would be less work for<br>
maintainer.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div>+1 . We could use the blocker flag to tag actual blockers.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Talur<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> - What is a blocker anyway?<br>
><br>
> Blockers can be broadly classified as, regression of functionality due to<br>
> code introduced in prior minor releases for the current version, bugs<br>
> identified causing corruptions, bugs identified causing crashes<br>
><br>
> If you believe a bug is a blocker, but still does not meet the criteria<br>
> above, err on the safe option and call it a blocker, whose merit can then be<br>
> discussed on the lists and appropriate action for the release taken.<br>
><br>
> - Other questions or comments?<br>
><br>
> HTH,<br>
> Shyam<br>
> ______________________________<wbr>_________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br></div></div>