Recommended Posts

Update:

In a move that I would hope should surprise exactly nobody, we're pushing back 1.1 by a little bit because of the realities of the work remaining to be done (I have a lot of patches that need to be landed, tested, bugfixed, there are other patches from other people to which the same applies; also we need a reasonable stabilization period and a resurrection of the l10n infrastructure in order to do a release of similar quality and range to 1.0.) Asa is working on an updated roadmap graphic, which will offer more details. The likely possibility is a 1.1 Developer Preview (= alpha, NOT for general consumption), followed by a 1.1 Preview Release (= beta, wider consumption, feature complete), followed by RCs and a 1.1. We're not fixed on dates yet, but this is just a heads up.

Source: Ben Goodger's Blog

Update:

We're coming up fast on the 1.8 Beta freeze -- February 9. When we ship Beta, we'll be locking down the trunk until we branch for Gecko 1.8. See the roadmap diagram for more detailed schedule information.

Beta is the last chance to get L10N impact changes landed for all of our applications. It's also the last chance to get any high-risk or potentially destabilizing changes landed. With the Firefox and Thunderbird 1.1 "Gecko update" releases scheduled to come from that branch, we can't afford to regress stability over the 1.7 and Aviary 1.0 branches.

Ben has posted some information on the 1.1 release at his weblog and I hope to have an updated Aviary roadmap graphic soon.

Source: Asa's Blog

Quick question: How come on Asa's blog it says:

Just a reminder, this is not a feature release, it's a Gecko update that should provide performance, stability, and website comaptibility improvements for Firefox.
but then from your post it seems like Firefox will have a new OS X like UI in the options window and the Sanitize stuff?

Update:

More Betas

I'll have more details shortly, but I just wanted to give everyone a heads up that we're going to be adding a second 5 week long beta cycle before we get to the Gecko 1.8 branch.

Also, I hope to have the diagrams for both the overall roadmap and the Firefox 1.1 roadmap posted today or tomorrow.

Source: Asa's Blog and also Ben's Blog

and for a little comedy via Blake's Blog

This would be good to have in Firefox

If you saw 24 tonight and were wondering, ?What would I do if Turkish terrorists overloaded the Internet in order to use the Dobson override to melt down 104 nuclear power plants?", I have some good news: they flashed the patch on the screen just long enough to catch the cure. It turns out the answer is in an MFC class called CDaoWorkspace! Just search down to the Create function, replace CDaoWorkspace with DobsonWorkspace, and you have a fully functioning nuclear override.

We really should get this in Firefox. Sure puts that antiphishing crap to shame, eh?

Ben also posted on his blog a comment about the Netscape "Antiphishing" browser

"Netscape claims to be the No. 2 browser company"

LOL... if they hadn't laid off their entire browser department it would be less funny.

Edited by supernova_00

Update:

I've included the latest roadmap in my original post. To better understand it, on April 1 that is when Firefox will branch from Mozilla 1.8 trunk (which will be final then). All work for firefox 1.1 will be done on the branch whilest 1.5 work will be done on the trunk kinda like how the whole 1.0 release went with branches and trunks...this time is different because the branching period will not be nearly as long and the trunk will not freeze before the Mozilla 1.8 release so as to not hold up production for Firefox and TB.

Recent News:

Closer to Preferences Completion...

I've been busy... but am finally nearing the light at the end of the tunnel on the new pref window - fixing a lot of bugs, making some UI changes based on suggestions, etc. I'd like to get some testing builds to people sometime this week.

Source: Ben's Blog

Update:

Well, here we are, coming up on the end of the Mozilla 1.8 Beta(1) cycle. We've still got a hefty list of things that I'd like to see fixed, but I suspect we'll punt on a few of them and try to get those in the Beta 2 cycle. The sooner we can get Beta out the door, and collect some feedback on the subset of Beta changes that are important to the 1.0.1 releases and the upcoming branch from which the 1.1 releases will ship, the better chances we'll have at getting any new problems discovered and fixed.

There's a lot that's about to happen so here's a rough outline of what we face in terms of releases. Sometime around the middle of next week we will have landed the majority of the changes on the trunk that we're hoping to get into the branch-based Firefox 1.0.1, Thunderbird 1.0.1, and Seamonkey 1.7.6. Once that happens, I'll try to get the trunk-based Seamonkey 1.8 Beta(1) shipped so we can test out those fixes before we ship them in our Firefox, Thunderbird, and Seamonkey stable update releases.

When we ship Seamonkey 1.8 Beta(1) the trunk will open for Beta 2 development work which should last about 5 weeks. Early during that cycle when things are less chaotic on the trunk, we'll test and ship the 1.0.1s and 1.7.6. Then we'll turn our focus to the Firefox 1.1 Developer Preview Release -- a Firefox 1.1 test build intended for community, not widespread, testing -- and getting the trunk in good enough shape to branch for Gecko 1.8.

At the end of the second beta, we'll freeze all localizable Firefox and Thunderbird strings which should make things easier on our localization teams. (If all goes well, Thunderbird will have official 1.1 localizations in Mozilla CVS, just like Firefox.) At about the time of the branch, we should be in good enough shape to ship the Firefox 1.1 Preview Release -- the more widespread preview of the Firefox 1.1 feature set and improved Gecko rendering engine.

Once branched, we'll be restricting all of the branch changes to only the most important fixes for the Firefox and Thunderbird 1.1 releases, with hopefully no major changes and a whole lot of bugfixing. The trunk will be opened to Gecko 1.9 development where lots of exciting gecko changes will be happening. On the branch, we'll probably have a Release Candidate or two in late May and if all goes well, the final 1.1 releases in the first week of June.

As you can see, we've got a very aggressive, and very full schedule between now and June. I'll be intimately involved in all of these releases (not to mention work on QA and test automation, community building, and spreadfirefox.com,) so I may not have as much time for blogging here, but where I can, I'll be posting progress updates and other bits that I think you all will find interesting.

This release schedule is a bit confusing but can be made more obvious if you spend a minute studying the roadmap graphics from my earlier post. If that doesn't clear things up, please feel free to post questions here.

Source: Asa's Blog

Yesterday, Firefox surpassed 25,105,560 downloads in just 99 days. Everyday since release in november, Firefox has been download over 200,000 times each and every day.

"We're not going to stop at 25 million either. There are still hundreds of millions of people suffering the IE experience and that's going to change. If you know of people that are tired of the pop-ups, tired of the adware and spyware, tired of viewing the web through the distorted goggles of a browser from the last century, then take a minute to show them there's a better browser available today, one that puts the power back in the hands of the users rather than the web badguy flavor of the month." - Asa

Edited by supernova_00
I hope to have some Firefox 1.0.1 (security and stability update) candidate testing builds sometime between Friday (18th) and Tuesday (22nd), depending on when we get the last of the fixes landed. If all goes well and this update tests out, we could have a Firefox and Thunderbird 1.0.1 update by the end of next week.

-Asa

Update:

(NOT same as what my thread follows)

Firefox 1.01 should be released this afternoon (Pacific time) All 1.01 is, is 1.0 + a bunch of security fixes, a few other bug fixes but nothing major in that department. This will be a security update only. No new features. One notable bug fix will be no more fat caret!

Update:

The New Options dialog will be in todays Trunk nightly. Know bugs are:

# #283590 [Firefox-Options landing]-Disk Cache size cannot be changed in new options dialog [Win]

# #283595 [Firefox-Options landing]-Privacy > Password > Set Master Password does not work in new prefs [Win]

# #283596 [Firefox-Options landing]-"Load Images from originating website only" pref not working in new options dialog [Win]

# #283600 [Firefox-Options landing]-Can't open Find as you Type/Find Toolbar [Win]

# #283601 [Firefox-Options landing]-Privacy > Cache > "Clear Cache Now" not greyed out after clicking [Win]

# #283603 [Firefox-Options landing]-The "tab"-icon in Options is the same as download-icon [Win]

# #283604 [Firefox-Options landing]-Edit Languages in new prefs window does not display 2nd and next items correctly [Win]

# #283607 [Firefox-Options landing]-Advanced > Security > Verification > Response Signer pulldown wrong size [Win]

# #283610 [Firefox-Options landing]-"Select new tabs opened from links" setting works the otherway around in new prefs [Win]

Update: Some more bugs created because of the new options dialog

# #283590 [Firefox-Options landing]-Disk Cache size cannot be changed in new options dialog [Win]

# #283595 [Firefox-Options landing]-Privacy > Password > Set Master Password does not work in new prefs [Win]

# #283596 [Firefox-Options landing]-"Load Images from originating website only" pref not working in new options dialog [Win]

# #283601 [Firefox-Options landing]-Privacy > Cache > "Clear Cache Now" not greyed out after clicking [Win]

# #283603 [Firefox-Options landing]-The "tab"-icon in Options is the same as download-icon [Win]

# #283604 [Firefox-Options landing]-Edit Languages in new prefs window does not display 2nd and next items correctly [Win]

# #283607 [Firefox-Options landing]-Advanced > Security > Verification > Response Signer pulldown wrong size [Win]

# #283608 [Firefox-Options landing]-Downloads > Download Folder directory can't be changed. [Win]

# #283610 [Firefox-Options landing]-"Select new tabs opened from links" setting works the otherway around in new prefs [Win]

# #283613 [Firefox-Options landing]-windows do not exit on pressing the escape button. [Win]

# #283639 [Firefox-Options landing]-"Sanitize Now" doesn't work if "Ask Me Before Sanitizing" is checked [Win]

# #283640 [Firefox-Options landing]-New Options UI: Hang when opening / closing cookies [Win]

# #283660 [Firefox-Options landing]-The new preferences window can't be closed on OS X (and doesn't have a collapse toolbar button) [Mac]

# #283678 [Firefox-Options landing]-Serif / Sans-serif pref ui doesn't work anymore [All]

# #283694 [Firefox-Options landing]-Cannot manually add cookies to the exceptions list [Win]

# #283716 [Firefox-Options landing]-advanced javascript options missing in new Options Window [Win]

Also wanted to explain that the big jump in nominees and blocker fixes was due to the new options dialog.

EDIT: Also wanted to let you guys know that Firefox 1.0.2 will be released soon...if you aren't having problems there is no need to update to it. Just fixes some bugs with the installation and autocomplete...only happens with people using the installer to install over 1.0 zip installation

Edited by supernova_00
New Mozilla Firefox Options/Preferences Window Lands

The latest trunk builds of Mozilla Firefox now feature the redesigned Options/Preferences window that has been developed over the last few weeks. Most noticeably, the new window moves the category icons from the left side of the window to the top. The number of category icons has also been increased: a new Tabs category contains the tabbed browsing preferences formerly located in the Advanced category. In addition, the Web Features category has been renamed to Content. Some of the settings have been moved around as part of the redesign so you may have to do a little hunting to find your favourite option.

The Privacy tab no longer uses expandable sub-categories but instead makes use of tabs. The actual options remain largely as before, though the redesigned Cookies window now groups cookies by site and includes a handy quick search bar. There's also a new 'Sanitize Settings...' button, which allows users to choose which pieces of private data the new 'Sanitize Firefox...' (they're looking for a better name) menu item should delete (by default it clears everything except saved passwords and cookies). There's no longer a 'Clear All' button, so you'll have to use the menu item or keyboard shortcut to actually delete the specified private data. It's also possible to set Firefox to sanitize itself when it's closed.

...Read More

Here is todays nightly release Please note though that these trunk builds are basically alphas so there are bugs. Also, do no install over a previous installation, remove it (profile will still be in tact) and install the nightly...best to use zip builds for nightly testing
This topic is now closed to further replies.