Recommended Posts

nope not me

586029814[/snapback]

Whoops, sorry! :) One page back someone said they still read your blog everyday, and right after you posted that blog entry with Brendan's roadmaps and diagrams... I just assumed you were Brendan!

Sorry!

EDIT: If there isn't already, you should link to Brendan's blog entry at the top of your article.

Thanks for keeping this thread updated!

Important Extension Updates

Some really nice fixes for extensions developers have been checked in for Mozilla Firefox 1.1:

Ability to restrict to compatible operating systems

If your extension only works on Windows you can now have this in your install.rdf file:

<em:targetPlatform>Linux_gcc2</em:targetPlatform>

<em:targetPlatform>Linux_gcc3</em:targetPlatform>

<em:targetPlatform>WINNT_msvc</em:targetPlatform>

<em:targetPlatform>OS2</em:targetPlatform>

Allow extensions to ship searchplugins

Search plugins are currently located in the searchplugins directory which is a sub directory of the Mozilla Firefox program folder. So if you wanted to add a search plugin you had to add it there. So if you removed Mozilla Firefox and reinstalled all your user installed search plugins would be lost. But now extensions can contain search plugins. They should be placed in <extensionguid>/searchplugins.

No way of installing platform specific XPCOM components (dll/so) based on user OS.

You can now specify in your install.rdf file which files should be installed on which OS'es. Nice for people who are distributing XPCOM components as parts of their extensions.

Source: Henrik Gemal's Blog

Just wanted to say that I changed the design on my site. I still have some work to do, but this design is a heck of a lot better then the last, if you guys have any suggestions please email or pm me...especially if you have some tweaks for usercontent.css and userchrome.css

  • 2 weeks later...

Deer Park Alpha 2 a few weeks away

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.

Source: Asa Dotzler's Blog

New since Alpha 1:

  • Drag and Drop reordering of tabs
  • Software updating via patches is almost complete
  • Some changes in the ui for updating themes and extensions
  • Lots of other small things
  • and of course hundreds of bug fixes

Firefox Mac Builds with CFRunLoop

I posted a test build of Firefox to the mozilla.org FTP site.

ftp://ftp.mozilla.org/pub/mozilla.org/fir...mac.PLEVENT.dmg

This build uses the CFRunLoop event system, which should be a major performance win, especially for plugins and drawing. We need the community to test this quite a bit so we can try to get this in for Firefox 1.1. Give it a spin and let me know how it goes!

Source: Josh Asa's Blog

We expect a Firefox 1.0.5 release in the not too distant future and we'd appreciate any help you all can offer by downloading and testing out these new bits. The changes that need the most testing coverage are in how the UI widgetry works.

Our preliminary testing doesn't turn up any issues, but patches similar to the ones we've recently taken in the 1.0.5 development builds have created some small bugs in out of the way places in the UI so please poke around and let us know if you find anything not working as it did in previous 1.0.x builds.

Mac | Windows | Linux

Source: Mozilla Quality Assurance Weblog

Edited by supernova_00
  • 2 weeks later...

Firefox 1.1 Alpha 2 Next Week

We are currently planning to ship Gecko 1.8 beta 3 and Deer Park alpha 2 early next week. We hope to be essentially done with work for these releases by Thursday, June 30th. Thus, starting on Thursday, drivers intend to become much more restrictive in granting trunk approval requests (and we?ll also be a little more restrictive between now and then). To nominate a bug for consideration as blocking these alpha/beta releases, please set the blocking1.8b3 flag to ?

We?ve been actively managing the bug list for 1.8b3 for some time now, and are down to 17 blockers and 30 nominations. Overall release status and schedule is being updated at http://wiki.mozilla.org/Firefox:1.1_Product_Team[/quotSource: Mozilla Developers Blog

Vacation Time

Just thought I would let everybody know that I will be on vacation July 3-11, I won't be around a computer for most of those days so I really doubt I will update 'The Road to Firefox 1.1' threads on both Neowin and Mozillazine. Also, if any interesting news arises for Firefox I won't be able to update my blog to inform you guys. I will update everything as soon as I return though.

Firefox 1.1 Alpha 2 close

Firefox 1.1 Alpha 2 is very close to being ready to be released...only 9 bugs left blocking the release + a few days of testing. I'm posting about this again because I feel that it will be released next week when I'm on vacation and I will not be able to blog about it to let people know. Keep an eye out for it at Mozilla.org and also Mozillazine.org

Firefox's New update system

We're well aware that the update system we had in place for Firefox 1.0 was sub-par and a major focus for the upcoming 1.1 release has been building a world-class update system that "just works" for our users.

Accomplishing this work is no small feat and we learned a lot from our experiences with the 1.0.x releases. The new system will be much more robust and capable on both the client side and the server side. From the client end, we've got a much improved user experience that should take away pretty much all of the pain of updating Firefox 1.1 for both minor versions and major versions. On the server side, we've increased our capacity and will have the capability to serve "patch" updates which should make things easier for everyone.

This new system will also provide benefits for our testing community. If all (or even most) goes according to plan, nightly build users will be able to get the latest nightly bits through the same update mechanism which will make testing nightly builds a bit more convenient and, more importantly, will help us get a lot more testing on the update system itself. This nightly updating system should be in place within the next few days and will be available to our 1.1 Alpha 2 users (preffed off by default). 1.1 Alpha 2 is just the first testing stage, though, and the 1.1 Beta is where we'll introduce the full set of capabilities (including patching) to the testing community.

I'm super-excited about these improvements and will do my best to keep you all up to date on our progress and the opportunities for early testing. Stay tuned.

Source: Asa Dotzler's Blog

  • 2 weeks later...

Mac testers - help us test Safari Profile Migration

Mac users will appreciate the new Safari migration feature in the latest versions of Deer Park. This feature allows users to import their bookmarks, cookies, preferences, and history into Firefox directly from Safari. It would be great if we could give this some more testing, so if you have a mac, please go ahead and give this a try:

1. Download this nightly build.

2. Launch Deer Park and choose File->Import.

3. Select Safari.

4. Select the settings you want to import from Safari.

5. Confirm that everything was imported successfully, that no data is missing, and that everything behaves as expected.

Thunderbird Users - Help us test Software Update (Windows Only)

The new application update service is now available for Thunderbird users on Windows and we could use your testing help!

The instructions are very similar to those Asa outlines in his July 5th post in this blog.

1) Make sure you are running a nightly Thunderbird trunk build from July 7th or later. Here is a link to the Windows build for July 7th: Windows Build

2) Go to: Tools / Options / Advanced / Config Editor. Change app.update.url to:

https://aus-staging.mozilla.org:8711/update2/0/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/update.xml

3) Now choose "Check for Updates" from the Help menu item and if there is a new nightly build available, we'll download the update and install it.

Note: you'll get the same cert warning dialogs with the testing server that you see when updating Firefox. Please refer to Asa's July 5th post for more about the cert warning dialogs.

Again, this is only for Windows. Please try it out and let us know if you have any issues.

Newer Firefox 1.0.5 Candidate Builds

We took another fix last night, so we have new builds on all platforms. If you have some time and take the build for a test spin, that would be great. Please report any issues as a comment to this post. thanks!

Windows

Mac

Linux

Firefox Deer Park Alpha 2 Release Candidates

We now have a round of builds that are very close to what we will shortly release as Deer Park Alpha 2.

These candidate builds are now available for testing for each of Windows, Mac and Linux--- with l10n builds to follow shortly. Please note that for our alpha releases there are feature and polish issues that have not yet been completely worked out. We release these milestones to get the core code out to our community to test out major gecko and platform changes as soon as possible. If these test out well, we'll be shipping Deer Park Alpha 2 shortly.

This will be second alpha in the Deer Park product development cycle and will include all major and significant features, whether pref'd on or off in order to achieve wider testing and to solicit quality feedback. The quality standard for this release is pre-production and therefore it should be of the quality required to support testing, and for Extension, theme and web application developers to begin compatibility and feature testing in advance of Firefox 1.1. It may break some but not all 1.0+ targeted Extensions. It should not contain any significant and known crashers.

Please download these builds and let us know of any significant issues which should stop this release. In particular, please ensure that these builds work for you to access all major web sites and services that you use regularly, e.g. e-mail, e-commerce, banking, etc.

The new software update engine has been incorporated into these builds but is presently off by default as we put together and coordinate test plans. Details to be posted here shortly.

Also, after a round of successful testing and debugging during the first Deer Park alpha, we're enabling the Fastback feature. With this feature enabled where before the browser needed to re-render each page from a local cache of documents, now you will see a dramatic speed improvement when you click the back and forward buttons to navigate between recently viewed web pages.

Windows

Mac

Linux

Branching for Gecko 1.8

As previously announced on the Mozilla Roadmap, now that Deer Park Alpha 2 and Thunderbird 1.1 Alpha 2 (1.8b3) have been released, drivers is planning on branching for Gecko 1.8. We will branch in approximately 10 days when we expect to meet the following criteria:

* Deer Park and Thunderbird 1.1 are ?feature complete? and ?string complete?, with all l10n and build system dependencies resolved, and all major UI work completed.

* There are no major bugs on the radar that would be really painful to patch in both places

Developers should look to resolve any bugs which meet this criteria on the blocking list for 1.8b4. We?re now tracking these branch dependencies with bug 300860.

The target is to close the tree on Tuesday, July 26th at 12:00am p.d.t. with the intention to branch later that day and the announcement of the branch to follow.

Please note that the trunk is frozen but open for approved check-ins (approval1.8b4). Active management of the blocking list for branching will commence on Monday, July 18th with daily updates posted here.

The plan is for Deer Park Beta (1.8b4) to be released from the branch ?but not at the branch point? with two or more Firefox 1.1 Release Candidates to follow before the final release of Firefox 1.1 (1.8). An updated schedule for Deer Park will be posted shortly to the Deer Park Release Tracking and Management Wiki. Additionally, the plan for Thunderbird 1.1 can be found on the ThunderbSource:Source: Mozilla Developers Blog

Firefox 1.0.6 test builds

We are getting ready to release Firefox 1.0.6, Thunderbird 1.0.6, and Mozilla Suite 1.7.10 to address some API issues in the Firefox and Thunderbird 1.0.5 releases and we would like some help from our testing community.

Here are links to all of the builds:

Firefox:  Windows, Mac, Linux

Tbird:  Windows, Mac, Linux

Suite: Windows, Mac, Linux

Things to look for in these builds:

*Extensions that interact with web content and events - test on a wide variety of content types

*For Thunderbird, please test the Enigmail Extension

*Test extensions that you normally use to make sure that they function properly

Please post any issues that you find to this blog. Thanks!

Source: Mozilla Quality Blog

Edited by supernova_00

np toxikk

----

I will be posting another graph later today. This graph will be for Gecko 1.8b4 which is the core for Firefox, Seamonkey, Thunderbird and all other Mozilla Foundation Releases. Gecko 1.8b4 will also be the Firefox 1.1b and Thunderbird 1.1b release. Please use the Gecko 1.8b4 graph to get an idea on when Firefox 1.1b will be released and afterwards the original Firefox 1.1 graph can be the looked at for following the final release. The change comes from Mike Connor's comments earlier today.

Firefox 1.1 Scraped; 1.5 it is

For the last several months, we've been discussing the versioning of the upcoming Firefox release.

One major consideration in this decision was that the sheer volume of changes in the Firefox core (Gecko) made a minor .1 increment seem misleading. While it may not be obvious by looking simply at release dates, today's Gecko core of Firefox has seen nearly 16 months worth of changes compared to what shipped in Firefox 1.0. This is because we created our Gecko 1.7 branch (the branch from which Firefox 1.0 shipped) back in April of 2004. At that time, Gecko development on the trunk continued and very little of that work was carried over to the 1.7 branch to be included in Firefox 1.0.

Another consideration was that we've made some major improvements to the Firefox application, especially in the update and extension systems that warrant more than a minor version bump. Calling it 1.1 would suggest to most users that this was a minor update when in fact it is quite major and all 1.0 users really should move forward for a much improved product.

Source: Asa Dotzler's Blog

-----------

Gecko 1.9 Information

Within a week or two we'll be branching off 1.8 and opening the trunk for Gecko 1.9 development. This will be very exciting because we have a lot of interesting changes planned, many of which are underway and will land soon after the branch is cut. Here's a rundown of some of the upcoming changes:

* The new Thebes graphics code will be landing. Thebes is a C++ wrapper around cairo. Very soon we should be able to produce Thebes-based Firefox builds for Linux and Windows. We'll be doing intensive development and testing of these builds during the 1.9 cycle until we reach the point where we can make them the default builds. This will give us a number of cool features:

o Much less graphics code for us to maintain --- most of the work will be in cairo, which is shared with many other projects

o Various options for accelerated graphics: Glitz on Windows and Linux, Quartz on Mac, XRender on Linux (with an accelerated X server such as Xglx or Exa)

o Better quality rendering: some antialiasing, bilinear image scaling

o A powerful new graphics API so we can draw fancier borders, draw rotated HTML, etc

o Fix various rendering bugs that are currently hard to fix

* Blake Kaplan's caret patch fixes many issues with caret positioning and drawing by making caret drawing go through our standard paint path. In conjunction with the Thebes work, carets in rotated text boxes will be drawn correctly.

* We have a units patch from sharparrow which will simplify our code and make Gecko work intelligently on high-density displays. On 200dpi screens we'll draw 2x2 screen pixels for every CSS pixel.

* We also have an events refactoring patch from sharparrow that will simplify our code and fix a number of bugs. Some more events refactoring patches will follow to simplify the code even more.

* I have a plan to eliminate our widget trees by having all Gecko content render into one top-level widget whose only children are plugins. This will simplify our code considerably, fix some bugs and should improve performance (especiallly with Glitz).

* I also have a plan to eliminate the separate view trees we currently maintain and move the view manager's functionality in the presshell. This will also simplify our code a lot and will smooth the path to fixing various bugs (including at least one Acid2 bug).

* Christian Biesinger has a patch to fix some plugin architecture problems by moving plugin loading to content. This also fixes an Acid2 bug.

* I hope that David Baron's reflow refactoring branch can land as soon as possible too, which will fix many bugs and simplify our code some more.

* There is a plan to simplify the SVG code and reduce the footprint of SVG elements by being more intelligent about how we handle DOM SVG values.

I'm excited that these changes will simplify Gecko considerably. It's definitely something that needs to be done. Moving from four trees (content, frames, views, widgets) to just two (content and frames) should be a huge help. Eliminating most of our gfx code will also be a big win.

Source: Robert O'Callahan's Blog

1.8 Branch delayed a few days

It?s now clear that we?re *not* going to meet our criteria to branch for Gecko 1.8 by 12:00am pdt on Tuesday, July 26th 2005.

Our original criteria included:

? Deer Park and Thunderbird 1.5 being ?Feature Complete? and ?String Complete?

? All l10n and build system dependencies resolved

? All major UI work completed

? No major bugs on the radar that would be really painful to patch in both places

The major items holding up the branch include:

? Split windows patch

? A few l10n dependencies and UI changes which prevent us from being ?String Complete?

As a result of these open issues we plan on delaying the branch. Please bear with us as we get a better understanding of the scope of the remaining work and put together a detailed action plan for branching Gecko 1.8 and releasing the 1.5 Beta. We will have a new date for the branch by the end of day Wednesday. A detailed 1.5 Beta release plan will follow.

We really appreciate everyone?s hard work on getting us to 1.5, and understand the difficulty delaying the branch poses for Gecko 1.9 developers. If this poses a significant hardship, please do let [email protected] know as it will help us in ouSource:f next steps.

Source: Mozilla Developers News Blog

Sorry I havent updated, I was sent on a business trip last minute notice. I will update sometime this weekend once I have some energy.

Some things that happend while I was gone...will report more on it later.

* Mozilla Corporation started. Firefox/Thunderbird will still remain free with no changes to way things are done.

* New feature: Feed View. Instead when you click on an rss link you get the text, firefox will now display the feeds. Example

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.