Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion bugzilla.mozilla.org improvements
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Axel Hecht  
View profile  
 More options Jun 12 2009, 4:52 pm
Newsgroups: mozilla.dev.planning
From: Axel Hecht <l...@mozilla.com>
Date: Fri, 12 Jun 2009 22:52:19 +0200
Local: Fri, Jun 12 2009 4:52 pm
Subject: Re: bugzilla.mozilla.org improvements
Print | View thread | Show original | Report this message | Find messages by this author
On 12.06.2009 17:52 Uhr, Mike Shaver wrote:

> On Fri, Jun 12, 2009 at 11:38 AM, John J.
> Barton<johnjbar...@johnjbarton.com>  wrote:
>> 2. Support for figuring out which build a FIXED bug shows up in.
>> Notifications when the first such build is available. Firebug gets a bug
>> report that we track down to mozilla, then we add a bugzilla report. Then we
>> watch dozens of emails over months as the fix moves forward. Then the bug is
>> marked FIXED and we are left in limbo. We can't tell our users to try it and
>> yet we won't get another prompt about the problem. Our users think we left
>> it on the floor.

> FWIW, "the first such build" for FIXED bugs is always going to be "the
> next nightly from trunk", where you should presume those builds are
> taken from around 3AM Pacific.

We have a somewhat odd problem in l10n, as we're usually fixing bugs on
branch, and then port to trunk.

So, for new locales, we start working on the 1.9.1 branch, work towards
resolving the bug FIXED there and then need to find a way to track if
the bug is fixed on trunk, too.

I don't really recall what we came up with, I think I personally leaned
towards a "fixed-1.9.2" keyword.

Axel


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google