Well, today’s Fx 3 Status Meeting didn’t provide any new information for the upcoming Fx 3 Alpha 3 release. The only thing of interest is the development for support of “off-line apps”. May be there will be some news in tomorrow’s Gecko 1.9 Status meeting. For those who are interested, here are today’s meeting notes.
March 2007
Read More
A quick reminder as part of the blog re-design on March 10th, the Upcoming Firefox & Thunderbird Releases are no longer listed in the side bar. They are now on their own dedicated page under the Upcoming link in the header (just below the logo).
Thought I should let y’all know about the status of The Major Update, you know that wonderful (at least ideally it is) feature which is suppose to allow users to go from Fx 1.5.0.X to 2.0.0.X as an update. Well, I have no idea what is going on with this. Discussion on this feature seems to have disappeared from the Weekly Update meetings a couple weeks ago. When I was looking around on the mozillaZine forums I came across this humorous (but sadly true) post from the the-edmeister in the Update to v 2.0.0.2 does not work thread. This was…
A couple weeks ago during the Fx 3 2007/03/06 Update, it was mentioned that Fx 3.0a3/Gecko 1.9a3 was being targeted for March 20th. Doesn’t look like that is going to happen. Actually, the 20th is really and odd date when you consider it falls on a Tuesday this month and that is the day Mozilla holds the Fx 3 status meetings. Further reviewing last weeks Fx 3 Status and the Gecko 1.9a3 Meeting notes I saw no mention of a release date. The only thing I did see was a couple patches, one of those was for the memory leak…
Note: Fx 1.5.0.11/2.0.0.3 are security updates which include fixes for six major issues including the Password Manger Vulnerability bug. As mentioned earlier today in the Weekly Update 2007-03-19 post, Fx 1.5.0.11 & 2.0.0.3 RC’s were pushed out to users on the “Beta” (update) channel last week. Everything has gone well with these release thus far so Mozilla plans on making the final releases on Tuesday (03/20). They plan to go live with Fx 1.5.0.11 & 2.0.0.3 around 4:00 PM Pacific (7:00 PM Eastern) which means this is when getfirefox.com will be updated to show the most recent version as the…
Big news from today’s Weekly Update meeting: Fx 1.5.0.11 & 2.0.0.3 – A release candidate (RC) was pushed out to users who were on the ‘Beta’ update channel last week. These users had downloaded a ‘Beta’ version of Firefox 2 in the past. The reports from these users have been good so far. So, if all goes as planned, Fx 1.5.0.11 & 2.0.0.3 will be released tomorrow afternoon/evening (around 4:00 PM Pacific/7:00 PM Eastern). Fx/TB 1.5.0.12 & Fx 2.0.0.4 – Development has begun and should know more about the release schedule by next week’s meeting. These will be the next…
Very (too) quiet on the Mozilla front right now, so quiet in fact I haven’t seen any new nightlies on Fx (2.0.0.3 pre) or TB since March 15th. I don’t expect this will last for very long though….Tuesday, March 20th looks like Fx 3 Alpha 3 (the one w/o Places) is going to be released and chances are Fx 1.5.0.11 and 2.0.0.3 will be as well. It could really be a big day and Mozilla could release Thunderbird 2, but I don’t think that is going to happen just quite yet. After all, they just had another community test day…
Yet another delay for the AOM Deployment. Yet again due to the upcoming Firefox 1.5.0.10 & 2.0.0.3 releases which have been delayed (again). Plan deployment is now set for the evening of the 22nd. News Source: Mozilla Webdev Blog
The deployment of the new and not really improved Fx Add-Ons Manager (AOM) has been pushed back to Monday. The delay has nothing to do with the AOM itself but rather that the planned March 15th date is going to conflict with the new Fx 1.5.0.11 & 2.0.0.3 releases. News Source: Mozilla Webdev Blog
Whoops! It seems when we switched the theme and redid the sidebar widgets the search widget got removed. The search widget should now be showing up at the top of the sidebar. If it is not, do a hard refresh (CTRL+F5) to force Firefox to reload the page from the sever instead of the cache.