Maybe bug 237202 AKA [META] AMD64 (x86-64) 64-bit tracking?

Windows XP 64bit is expected in March - April 2005.

I just nominated a couple of bugs...

It would be good to get some traction on the one bug that's legitimately blocking1.8a6+ already (there's another where the flag was set by someone inappropriately before the new bugzilla restrictions were added) - bug 272764. Although it doesn't seem to be a smoketest blocker (because there's no XPI smoketest), I think it is make the small number of seamonkey nightly users even smaller.

With the roadmap graphic, although it might be awkward, I think it's important to show the branch points. I think a key purpose of the graphic is to show people how the branches relate to each other. Without the branch points shown, only people that already understand how the branches work will understand what the parallel lines are, and they could get the dates from the text anyway. It doesn't need to show all the previous releases from the branches, or the 1.7.1-1.7.3 mini-branch, but I think showing how the branches came from the trunk would be good.

Yea,

I am one of the few that actually like the Suite more then the individual parts.

Asa,
when is the landing of these bugs:
[Fixed on Aviary1.0 but not on trunk]
supposed to take place ?

Click on my name for the url

sorry, that didn't work.

https://bugzilla.mozilla.org/buglist.cgi?product=Browser&product=Firefox&keywords_type=allwords&keywords=fixed-aviary1.0&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfieldto=Now&order=Bug+Number

michaell, the roadmap diagram isn't intended for people not already familiar with our branches. It's a "developer roadmap" intended to help keep all of our developers in sync. I did try for a while to keep the branch point for reference, but 1.7 branched way back in the first half of April. There just wasn't any easy way to keep that legacy data on the diagram and probably not a lot of value in doing so. I do plan, however, to build a table of dates, like the one under the current roadmap diagram, that goes back "to the beginning" :-)

--Asa

Hrmm.. now if you want to be really nice to me.. you could go through the work and make a tree going back to the origional M builds.

I think it would be intersting to see how it changed from M's to 0.9.#... to Alphas and betas, to Alpha 1, 2, beta, release.

I graphical history of stuff seems to make things a lot more interesting and more fun to follow.

*hugs*

Ensure the Print Preview dialog is fully working and the many 'access' bugs are fixed for it.

This is an front end feature which went in with 1.0 final and in my opinion isn't up to the job quite yet (don't get me wrong it's good, but too buggy for 1.0).

My parents (who I have using Firefox) print a lot from the web and often phone me to ask why a particular feature isn't working in Print Preview. I just tell them it might be fixed in the next release / it's being worked on.

There is no plan for a version 2 of Javascript? This is a great way
to develop better XUL application?

Asa: "the roadmap diagram isn't intended for people not already familiar with our branches"

I guess not. Unfortunately, whether it's the intention or not, the audience for the roadmap document also includes enthusiastic users, the wider community, and even the media, who all end up misunderstanding and getting confused. But I guess that's something that needs a wider solution than fudging the scheduling diagram...

Well, I used to be able to find what was going on and anticipate releases and stuff. Somehow all of my tools for this are gone. Branch landing isn't used anymore, status reports died a long time ago and the releases page has been left at the first 1.7.

I really like to have an overview of what is going on and what features to watch (and test) but I just can't see it these days.