Recommended Posts

was about to post that ;) The one blocker also has a patch up for review...so *finger crossed* tomorrow's official nightly might be the 1.1a release (as long as brenden reviews the patch...he is in amsterdam right now)

to the two above the last poster: that is not a final build you are using, and its not meant to be completley stable. its a developers previews, hence the reason for the name change so everyone doesn't try using it that has no clue what they are doing.

ALF: There is still at least 3 months of development left for 1.1. The day 1.1a is released a crap load of new things is going to be added like: drag and drop reordering of tabs, incremental updates, fix for wrong renaming when two files with same name, and a bunch more things that aren't accepted to blocking 1.1 but have patches to land after the freeze is lifted.

----

And there are no more 1.1a blockers so looks like todays official nightly will be 1.1a :) I'll keep yall posted!

I changed the queries today hence the reason for the drop in fixed blockers, I had Thunderbird included in the query by accident.

New Deer Park Alpha1 testing builds

Yesterday we took what was supposed to be the final change into Deer Park Alpha 1 - the change to the theme and extension version from what we had on the 1.0 branch. This caused some fallout and we're looking for additional testing to make sure there aren't any unknowns in the area of extension updating.

Please grab one of the builds below and give it a whirl. If you find any additional problems with extension or theme update or install, please let me know here. Thanks.

Download:

Windows

Linux

Mac

Source: Asa Dotzler's Blog

~~~~~

Damn it, today's nightly was prepared for 1.1a and was about to be release until this crap....grrrrr!

P.S. Don't forget to subscribe to my blog to keep up to date with firefox happenings (link in sig)

Edited by supernova_00

Ok once again...and this time i'm positive that these builds will be 1.1a1. Here is the latest builds to test out...if you find any crashers or serious regressions please report them! The builds in the link below are the respins so 1.1a1 is tonight!

Get the test builds here for win, linux, and mac

Edited by supernova_00

One bug that I have noticed, and not been able to replicate anywhere buy on my home pc, is a refreshing/jumping glitch.

It does it on some pages, some pages it doesnt, it doesnt always do it on the same page.

The little icon for the page in the address bar will just keep jumping, seemingly refreshing or something.

I can close it and go back to that page and it wont happen anymore. Does this on all nightly builds also (Deer park only, not firefox).

I uninstalled all themes and extensions thinking it may have been them, but it wasnt.

Currently running on linux and it feels allot better, less memory hog and cpu time, all the extensions works like flashblock and adblock etc.. took over all my settings without probs, only one small glitch in the preferences menu.  :woot:

586003701[/snapback]

good to hear, what is the small glitch?

Also, there were over 58fixes and 11 partials since 1.1a1 release. Only because the long freeze, patches built up over the past week. 37 blockers left for 1.8b3 and about 20 of the bugs have patches waiting for review/landing. :) So shouldnt be that long before 1.8b3...I'd say about week and a half to two weeks max!

New Roadmap + Info

This roadmap update has been much-delayed, as we have juggled priorities and sweated security releases on the AVIARY_1_0_1 branch. Sorry for the delay; I will keep the roadmap up to date much more frequently from now on.

The new roadmap restarts the document with as little repeating boilerplate as possible. Highlights:

  • The main point is to focus near-term work on the Mozilla 1.8 milestone, which is the basis for the rv:1.8 Gecko codebase in Firefox 1.1 and XULRunner.
  • We would like to branch 1.8 by the end of June, in order to open the trunk up for general Mozilla 1.9 alpha 1 milestone development. Sooner would be better, and later is hard to justify.
  • A high priority for Firefox 1.1 at this point is to finish the end-to-end support for the incremental app/extension update work being done based on bsdiff, which has been spearheaded by Darin Fisher.
  • We have also made several major architecture changes (e.g., XPCNativeWrapper automation) for improved chrome scripting security, with one more to land, so security is another high priority that may justify late-breaking changes.
  • Apart from update and security, we won't take any big changes on the 1.8 branch, instead focusing on quality and polish. So now is the time to cut low-priority or "nice to have, but ..." items from your 1.8 buglists.
  • Pending testing results from Deer Park Alpha 1, which just released, we will have a better idea of the order of work remaining.
  • There will be a second Deer Park Alpha, to line up with the 1.8b3 trunk milestone. Here's the usual diagram, free of hard dates:
    branching-2005-05-04.png.
  • We will construct a detailed schedule for the rest of the release. Until we have a more "real" schedule, the roadmap will be fuzzy about dates.

Apart from the absolute priority that Firefox 1.1 be able to update itself in small background-downloaded increments, and that its security and quality be at least as high as Firefox 1.0.x, we have already enabled new platform features such as SVG and <canvas>. These new richer-graphics-for-the-web features are in usable shape, and they deserve testing and experimental usage in XUL and even HTML. We want developer feedback, which we will incorporate into future releases.

In order to help both our XUL platform and (more important) the open-standards-based web to compete with next-generation OSes and their proprietary frameworks, we are rearchitecting Gecko's graphics subsystem. Here is a picture of Gecko emphasizing its graphics infrastructure as of the 1.8 milestone and Firefox 1.1:

gfx-arch-1.8.png.

Here is where we are headed in 1.9:

gfx-arch-1.9.png.

We are joining forces with the Cairo Graphics project (this will be no surprise to anyone following the project, in particular roc's blog). Together, we can move faster and on more platforms, toward a hardware-accelerated 2D future, and beyond.

As with any large rearchitecture, there will be bumps along the way. But we are not going to rewrite the world at once (never again!). We aim to make changes in smaller increments, that can be done during the 1.9 alpha cycles. So the 1.9 schedule, which I won't even bother to depict yet, will have a good number of alphas.

Anyway, this is a blog item's worth of roadmap content, which will show up in a more polished form in the main roadmap soon. Your comments are welcome.

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

    • No registered users viewing this page.