Created attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) I forgot to list one of JEP 0.9.6.3's fixes.
Comment on attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) mento, can you have a look at this new JEP since josh is on vacation? Ideally, this should land on trunk sooner rather than later so it can bake and get testing coverage in order to be able to make 188.8.131.52 on the branch.
Thanks, Mark! Like Smokey, I'd like to get this landed on the trunk reasonably soon (though I suspect that will have to wait until Josh gets back). And since (barring any urgent security issues) it looks like there aren't any imminent releases on the 1.8 branch, I'd like JEP 0.9.6.3 landed there at the same time it lands on the trunk. This should substantially increase its exposure to users, and the likelihood that any remaining bugs will be shaken out before the next releases on the branch.
I can land this on the trunk for you now if you'd like, but you'll need branch approval before it can be landed on the 1.8 branch.
Thanks! Please do. I think I'll wait until Josh gets back to deal with getting it landed on the branch.
Comment on attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) rs=pink
Josh or Mark: Please land this on the trunk as soon as you can after the tree reopens. It might fix (or alleviate) a trunk topcrasher (bug 390225).
Comment on attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) JEP 0.9.6.3 might fix or alleviate a trunk topcrasher (bug 390225), which is blocking 1.9+. So I'm requesting approval to land this right away.
(Following up comment #8) The risk of landing JEP 0.9.6.3 is quite low -- I tested it thoroughly before I released it, it contains only a few changes, and I've had zero reports of problems since it was released a month ago.
mento might get this landed this weekend (smichaud's on vacation, if I have my dates right), but adding the keyword so this doesn't get lost, whatever the story may be.
Landed on trunk.
Marking FIXED to reflect the trunk landing. Or was there more to do?
Comment on attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) > Or was there more to do? It still needs to be landed on the branch :-)
Comment on attachment 271050 [details] Change log for JEP 0.9.6.3 (revised) approved for 184.108.40.206, a=dveditz for release-drivers
Landed on MOZILLA_1_8_BRANCH.
verified fixed using Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a8pre) Gecko/2007090404 Minefield/3.0a8pre and Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:220.127.116.11pre) Gecko/2007090403 BonEcho/18.104.22.168pre.
Firefox 22.214.171.124 RC2 (dated 2007-09-15) bundles JEP 0.9.6.2. It shouldn't -- it should bundle JEP 0.9.6.3. Anyone know what's up? Is RC2 (like RC1) just "a test of a new automated system for producing release builds", which we should ignore?
I just checked, and today's 1.8 branch nightly (2007-09-15-04-mozilla1.8) still does bundle JEP 0.9.6.3 (as have other 1.8 branch nightlies since I landed JEP 0.9.6.3 on the 1.8 branch on 2007-08-30).
126.96.36.199 is coming off of the Gecko 188.8.131.52 relbranch and not picking up any general changes since then.
Thanks for the info, but this is a bit ... disconcerting. Firefox 184.108.40.206 really should bundle JEP 0.9.6.3, which contains some important fixes. Is there a release roadmap for Firefox 220.127.116.11 somewhere online? http://wiki.mozilla.org/Firefox doesn't have anything.
> http://wiki.mozilla.org/Firefox doesn't have anything Now it does. Thanks, Smokey. (I assume you were the one who updated it.)
(From Firefox 18.104.22.168's roadmap) > This is a security firedrill to address the issue described in bug > 395942 ("quicktime pwns firefox") > > We'll take Fx 22.214.171.124 and add this one fix only. So it's an emergency release.