Target Milestones, cont'd, and release-process documentation

Gervase Markham gerv at
Wed Oct 22 12:22:35 UTC 2014

On 22/10/14 12:46, Frédéric Buclin wrote:
> Le 22. 10. 14 12:43, Gervase Markham a écrit :
>> This seems odd to me. Surely severity=blocker is the way of finding
>> blockers?
> Errr.... so you will no longer use the blocking4.x flags?
> IMO, setting severity=blocker for new features doesn't make sense.

Well, making new features blockers for time-based releases doesn't make
sense either :-)

But my point is not so much about blocking; it is: Target Milestone
should indicate all bugs which are targetted at a particular release. A
bug is considered "targetted" at a release for one of two reasons:
either, the Bugzilla team will not release unless that bug is fixed, or
alternatively a particular developer has expressed intent that they
personally are going to fix the bug in time.

If someone goes to a bug and wonders "when will this be fixed by?", they
should be able to look at the TM field and either see a release number,
or "---"/"Future"/whatever, and understand the best estimate for its
being fixed.


More information about the developers mailing list