Comments on: When should we resolve l10n bugs as fixed? http://informationisart.com/stas/when-should-we-resolve-l10n-bugs-as-fixed Localizing Mozilla Tue, 23 Feb 2010 07:14:38 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: Staś Małolepszy – BugXhibit: an interface to Bugzilla’s search results http://informationisart.com/stas/when-should-we-resolve-l10n-bugs-as-fixed/comment-page-1#comment-532 Staś Małolepszy – BugXhibit: an interface to Bugzilla’s search results Fri, 29 May 2009 07:04:57 +0000 http://informationisart.com/stas/?p=273#comment-532 [...] in open bugs to indicate that the bug was fixed on branch but not yet on trunk. (I wrote about it before.) Bugzilla’s Quick Search is great help in this situation, because it lets me be more precise [...] [...] in open bugs to indicate that the bug was fixed on branch but not yet on trunk. (I wrote about it before.) Bugzilla’s Quick Search is great help in this situation, because it lets me be more precise [...]

]]> By: Dao http://informationisart.com/stas/when-should-we-resolve-l10n-bugs-as-fixed/comment-page-1#comment-520 Dao Sat, 16 May 2009 22:12:26 +0000 http://informationisart.com/stas/?p=273#comment-520 "The fix landed on 1.9.1 only, so the bug has the fixed1.9.1 keyword, sure. But since it hasn’t been yet fixed on central (for Firefox.next, mind you), the bug’s status is “new”, and it is still blocking the 3.5 release tracker. Why the lack of landing on central should block a 3.5 release?" Why is it still blocking the 3.5 release tracker if it has the fixed1.9.1 keyword? Sounds like the query just needs to be fixed. “The fix landed on 1.9.1 only, so the bug has the fixed1.9.1 keyword, sure. But since it hasn’t been yet fixed on central (for Firefox.next, mind you), the bug’s status is “new”, and it is still blocking the 3.5 release tracker. Why the lack of landing on central should block a 3.5 release?”

Why is it still blocking the 3.5 release tracker if it has the fixed1.9.1 keyword? Sounds like the query just needs to be fixed.

]]>