> The final blocker for Firefox 3.6 Alpha 1 has landed, so we've > closed mozilla-central for the evening in order to get a few test > runs in (it's red at the moment due to what looks like a tinderbox I/ > O or disk copy failure). If things go well, I expect to ask the > build team to tag for the release and then we can re-open the tree.
The tree went green, so we re-opened it this morning. Please note that anything you check in between now and when we branch for mozilla-1.9.2 is something you're committing to stabilizing for a late October release in Firefox 3.6 ... if you have a riskier piece of code, you should wait until after we branch for mozilla-1.9.2 next week.
>> The final blocker for Firefox 3.6 Alpha 1 has landed, so we've closed >> mozilla-central for the evening in order to get a few test runs in >> (it's red at the moment due to what looks like a tinderbox I/O or disk >> copy failure). If things go well, I expect to ask the build team to >> tag for the release and then we can re-open the tree.
> The tree went green, so we re-opened it this morning. Please note that > anything you check in between now and when we branch for mozilla-1.9.2 > is something you're committing to stabilizing for a late October release > in Firefox 3.6 ... if you have a riskier piece of code, you should wait > until after we branch for mozilla-1.9.2 next week.
> From a cursory reading of that bug there's no clear STR and it's an > intermittent problem, isn't it? Doesn't feel like a hard alpha blocker > to me, but we can respin if needed, I suppose.
We even have a regression range [1], and Brendan says he has steps to reproduce [2]. Clint also said he might have steps to reproduce, but hasn't indicated if it was reliable yet in the bug [3].
I meant to bring this bug up on Tuesday's meeting, but I forgot. My apologies.
I can tell you it's not reliably reproducible, because I cannot reproduce it on my system. I don't think it's something on which we need to block the alpha, we'll fix it in beta.
I'd feel more comfortable if someone could tell me if there's a workaround (like, if opening/closing fixes) but right now I think this is a PITA, but not a hard blocker. The files are still downloading, to the appropriate place, etc.
> On 8/6/09 8:01 AM, Mike Beltzner wrote: >> From a cursory reading of that bug there's no clear STR and it's an >> intermittent problem, isn't it? Doesn't feel like a hard alpha >> blocker >> to me, but we can respin if needed, I suppose. > We even have a regression range [1], and Brendan says he has steps > to reproduce [2]. Clint also said he might have steps to reproduce, > but hasn't indicated if it was reliable yet in the bug [3].
> I meant to bring this bug up on Tuesday's meeting, but I forgot. My > apologies.
