mozilla-central to be closed to Firefox 3.6/mozilla-1.9.2 blockers until code freeze
Mike Beltzner
As discussed at yesterday's development meeting, we'll be restricting
the mozilla-central tree to:
- fixes for Firefox 3.6 or mozilla-1.9.2 blockers [1],
- patches marked with approval1.9.2+ [2],
- patches that are not part of the Firefox build (including tests)
This is to keep the tree as quiet as possible so that our final blockers
can land for the Firefox 3.6 Release Candidate code freeze which was
originally scheduled for end of day today. Based on estimates from
yesterday, we expect the freeze will slip to the end of day tomorrow,
November 19th. If it lasts longer, I'll update this thread.
I'll mark the tree as restricted in an hour or so; please follow up with
comments or questions to this thread in mozilla.dev.planning /
dev-pl...@lists.mozilla.org
cheers,
mike
[1]:
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=flag%3Ablocking1.9.2%2B,blocking-firefox3.6%2B
Mike Beltzner
> As discussed at yesterday's development meeting, we'll be restricting the mozilla-central tree to:
>
> - fixes for Firefox 3.6 or mozilla-1.9.2 blockers [1],
> - patches marked with approval1.9.2+ [2],
> - patches that are not part of the Firefox build (including tests)
Just to follow up, the tree is now marked as restricted: http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox
cheers,
mike
Alexander Limi
3.6?
https://bugzilla.mozilla.org/show_bug.cgi?id=500983
(Was pointed to this just a few hours ago, and it explains why a lot of
people I have seen installing Firefox on work computers can't get it to
work)
Is this fair game for a 3.6.x fix after 3.6.0 goes out, in that case?
--
Alexander Limi · Firefox User Experience · http://limi.net
> _______________________________________________
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
>
Mike Beltzner
> So I assume this means it's too late to get the proxy bug fixed in time for 3.6?
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=500983
>
> (Was pointed to this just a few hours ago, and it explains why a lot of people I have seen installing Firefox on work computers can't get it to work)
That bug doesn't block, hasn't been renominated to block, and doesn't have a viable patch on it right now. If it gets a viable reviewed baked patch it can be approved, but somehow, I doubt it.
Could you comment in the bug about how you get to your conclusion from the premise of that bug? I don't actually see how it follows, but am probably missing context.
> Is this fair game for a 3.6.x fix after 3.6.0 goes out, in that case?
Of course. It's also nominated to be back ported to 1.9.1, I see.
cheers,
mike
Alexander Limi
> On 2009-11-18, at 5:24 PM, Alexander Limi wrote:
>
> So I assume this means it's too late to get the proxy bug fixed in time for
> 3.6?
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=500983
>
> (Was pointed to this just a few hours ago, and it explains why a lot of
> people I have seen installing Firefox on work computers can't get it to
> work)
>
>
> That bug doesn't block, hasn't been renominated to block, and doesn't have
> a viable patch on it right now. If it gets a viable reviewed baked patch it
> can be approved, but somehow, I doubt it.
>
> Could you comment in the bug about how you get to your conclusion from the
> premise of that bug? I don't actually see how it follows, but am probably
> missing context.
>
Will do. The connection between what I've seen and this ticket didn't click
for me until about an hour ago, which is why I'm raising it now.
> Is this fair game for a 3.6.x fix after 3.6.0 goes out, in that case?
>
>
> Of course. It's also nominated to be back ported to 1.9.1, I see.
>
Cool, a 3.6.x fix is more than good enough for me. I'll add some comments in
the bug on how this affects new users.