Firefox 3 RC1 released to hardy-updates

Monday, June 9. 2008

Here some good news for all of you waiting for the firefox 3 RC1 upgrade in hardy …

“Today, we finished the verification process and copied firefox 3 RC1 from hardy-proposed to hardy-updates!”

Thanks to everyone involved in this update. Also, many thanks to all the (brave) users that supported us by testing these packages while they waited in hardy-proposed!

In the unlikely case that you get to know about a regression, please file a bug against firefox-3.0 or the xulrunner-1.9 package and let the ubuntu mozillateam know directly.

Thanks for your support (and patience). Enjoy!

Posted by asac (Alexander Sack) in Ubuntu Mozillateam at 18:07 | Comments (9) | Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

I just see one problem here. Firefox 3 RC2 is out. Woops.

#1 BostonPeng (Homepage) on 2008-06-09 18:34 (Reply)

INVALID, not a regression

#1.1 asac (Homepage) on 2008-06-09 18:40 (Reply)

What?

Ubuntu users are just now getting RC1? Nearly a week after the rest of the world got RC_2_?

Why on earth didn’t you just skip RC1 and go right to RC2?

#2 Asa Dotzler on 2008-06-09 21:56 (Reply)

This is a big reason why I run Firefox code straight from Mozilla. Ubuntu’s repos can take too long to get updates. My way I get updates as soon as their pushed out to the users.

#2.1 BostonPeng (Homepage) on 2008-06-09 22:07 (Reply)

I didn’t put that as well as I should have. Sorry.

I wonder, asac, if there’s something that we can do to help you improve that lag.

Also I wonder if you’re going to be able to get closer to the official Firefox release date when you offer Firefox 3 final in Ubuntu?

If you do intend to shrink the window for final, where are you going to make up the time?

I know that we’ve taken about 40 changes since RC1 that we’re vetting pretty well with Windows and Mac users and I’m concerned about a much shorter testing window for all the RC1 and RC2 changes that Ubuntu users are getting.

And while I didn’t put it at all well in my first comment, I do wonder what the reason was for not just skipping RC1 and getting the last batch of official changes in before rolling it out to Ubuntu users. I hope you all took the fix for 421482 at least.

#3 Asa Dotzler on 2008-06-10 00:21 (Reply)

@Asa: The b5 to RC1 upgrade involved more than just the "firefox" upgrade. Look at the bug to see what other packages were involved in this transition.

The reason why we didnt "just" skip RC1 is that we cannot skip a fully QAed package update without risking further delay.

However, now that the heavy-lifting of the b5 to RC1 transition is done, the next upgrades should be muss less intrusive and much more "business as usual" and I expect that our actual release lag will eventually shrink to our "normal" lag – which usually is: release the same day.

#3.1 asac (Homepage) on 2008-06-10 09:42 (Reply)

Good morning,

Don’t know if this is the right place to file bugs, but since the update I am no longer to download files, bookmark pages, or use any shortcut keys. Also half the time I right click on links I receive an error about search assertion failed.
Running Kubuntu 8.04 Remix (kde 4.1)

Thanks,

Jonatahn

#4 Jonathan Jesse (Homepage) on 2008-06-10 03:56 (Reply)

@Jonathan: If you still see this issue, please join #ubuntu-mozillateam on freenode and ask for help there.

#4.1 asac (Homepage) on 2008-06-10 09:44 (Reply)

Further investigation… After a reboot of the system things have cleared up and ready to go. Thanks.

BTW I like the whole reply to option here.

Thanks,
Jonathan

#4.1.1 Jonathan (Homepage) on 2008-06-10 14:22 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above: BBCode format allowed Enclosing asterisks marks text as bold (word), underscore are made via _word_. Textile-formatting allowed Standard emoticons like :-) and ;-) are converted to images.
	Remember Information? Subscribe to this entry