We're starting to get a handle on the remaining bugs blocking our Deer Park Alpha 2 release and I'm hopefull that we can start getting candidate builds for more widespread testing in the next week or two (though, if you've been following my predictions for any time at all, you'll know I'm always unreasonably optimistic :-)
This second alpha release, like the first, will be targeting developers. We're interested in feedback from web developers, theme and extension developers, and Mozilla-based application developers.
I'll have more info as we get closer so stay tuned.
Posted by asa at June 16, 2005 06:58 PMStop saying Real Soon Now and learn how to ship. I recommend MSFT as an example of a company who excel in this regard.
Posted by: talloc() on June 16, 2005 07:09 PMI agree. It should be better to announce that candidates are out. Error bars of a week (plus or minus a week) are too coarse and it doesn't sounds very professional.
Posted by: user on June 16, 2005 07:19 PMAt least Asa gives an estimate of when the release is unlike the U.S. Government ;-)
Posted by: Jay MacLean on June 16, 2005 07:24 PM@talloc(): Oh yeah.. so according to MSFT, alpha 2 will be in... late 2006?
Are we talking about the same company?
He's announcing that *TEST CANDIDATES* will be released soon, give him a break.
Go find somewhere else to complain, than nit-picking about the release schedule for release candidates for an alpha of a product that is still a few more alphas away. *Sheesh*, you are all pathetic complainers.
Posted by: Jed on June 16, 2005 07:29 PMFirst of all this is alpha so yes give him a break. Second of all this is not the official blog of the mozilla foundation. This asa blog.
Posted by: Gabriel Mayrand Chadwick on June 16, 2005 07:31 PMAsa,
I hear you mention the terms "candidate builds" or "candidates" alot. Are "candidate builds" the same thing as a "release candidate," or are there some differences between the terms? It always seems that "candidate builds" are just nightlys, while "release candidates" get their own release directory. Is this correct?
Posted by: Billy Miller on June 16, 2005 08:16 PMI can't wait. So when does anyone predict Firefox 1.5 to be released if at all? as well as what will become Firefox 1.1?
Posted by: Jmack on June 16, 2005 08:39 PMtalloc() - when was Longhorn shipping again?
Posted by: Ryan VanderMeulen on June 16, 2005 09:17 PMJmack,
I am not sure I follow your question. 1.5 - "if at all?" It will be released. But after 1.1, which will be the next official release. For more check out the road map: http://www.mozilla.org/projects/firefox/roadmap.html. And by the way, 1.5 is being listed as a 2006 release. All of that is of course subject to change.
Posted by: timfry on June 16, 2005 09:37 PM> talloc() - when was Longhorn shipping again?
They only have some issues with the new IE7-browser ;-) Users say it should support web standards (CSS, PNG, RSS, etc), tabbed browsing, be even more secure and other difficult stuff (from Microsoft's point of view). Well, actually it should look something like Mozilla Firefox...
Posted by: Martijn Weisbeek on June 16, 2005 10:44 PMI'm running latest nightly build and are crashing a lot. Almost everytime it's related to poping up a new window. Hopefully it's fixed really soon.
Posted by: Henrik Gemal on June 16, 2005 11:43 PMHenrik, you have an extension problem, because the recent nightly builds are VERY stable :)
In fact, they're getting better and better!
Posted by: Caleb on June 17, 2005 02:58 AMVery good. I like Deer Park, but it didn't work with Blogger very well. I am planning to run an ad on BlogShares.com. Evertime someone clicks on a link I get 5 chips. With these chips I plan to run an ad about Firefox (telling them to download it.) Help me (click once a day please). CLICK HERE.
Posted by: Alex on June 17, 2005 04:23 AMAsa, my biggest concern with the current Deer Park builds is the assortment bfcache bugs (although they are slowly getting squashed). IMO, bfcache is going to need more regression testing than we'll have time for if too many bugs miss the next alpha.
Something I'd like to see is a full-scale test run of the new update system, perhaps with specific nightlies or between this alpha and the next (or the beta).
From a developer point of view, I think Themers would like the assurance that there will be no major UI changes for them to deal with, so they can start updating their themes for 1.1.
I'd also like to bring your attention to the "Menu bloat" thread once again (in Mozillazine General). We're getting close to a point where we have some fairly well debated points we'd like to communicate to Mozilla.org. How would you like us to proceed with this? Not sure when you're freezing localisation, but it could impact upon it.
Posted by: Ben Basson on June 17, 2005 07:15 AM@Martijn Weisbeek - I suppose you're right since nearly every other new Longhorn feature has been postponed or is going to be backported :P
Posted by: Ryan VanderMeulen on June 17, 2005 10:29 AMtimfry, I meant to put firefox 1.0.5.. if it were even coming out at all.
Posted by: Jmack on June 17, 2005 12:22 PMAsa, do you plan to bump the branding on the trunk to 1.8b3 before 1.1a2 is released?
Posted by: Rishi on June 17, 2005 08:41 PMJmack - I'm expecting a 1.0.5 eventually, but not just to fix the one highly publicized regression. It's a fairly minor vulnerability and rather difficult to exploit.
Posted by: Ryan VanderMeulen on June 18, 2005 08:16 AMSaturday's builds 20050618 still show rv:1.8b2 in the user agent string.
Posted by: David B. Haun on June 18, 2005 08:26 AMI found the builds very stable & I happy to see they finally allowed you to switch the order of the tabs although I think this has only been added on recent builds.
Posted by: Buzz on June 23, 2005 02:22 PMHello, could somebody give me the address where I could download Mozilla 1.7.9 (pre-release version) for Windows ??
Posted by: MoziDrago on June 24, 2005 05:54 PM