Mozilla Roadmap minor update: SeaMonkey suite sustained
Brendan Eich
some time around the middle of July, when the Mozilla Foundation was
spun out, and about nine-hundred things related to that momentous event
happened all at once. My sincere apologies for failing to keep it in
synch with the shifting terrain.
I've finally updated just the parts that talk about the SeaMonkey
application suite (the current default build) to say that the suite will
continue to be supported for the many organizations who have deployed
it, or a derivative of it such as Netscape 7.x. The Mozilla Foundation
intends to sustain the suite with enough engineering to supports such
deployments, especially enterprises and large organizations who are
already committed to the suite, and who require a smooth upgrade path.
"Sustain" here, so far as we can see, means no major UI overhaul or
radical front-end innovations -- we see no conflict here with the active
contributors, who are doing a great job keeping SeaMonkey in fine shape.
The focus for innovation and development, in both application and
back-end "GRE" type work, remains on the new standalone apps, Mozilla
Firebird, Thunderbird, etc. This focus on the new apps and their add-on
architecture has not changed, even thought SeaMonkey is no longer at
risk of bit-rot. We are just doing two things now, innovating and
sustaining, in order to satisfy several distinct sets of customers of
Mozilla products.
While I was editing, I updated references to the 1.4 branch that were
written in the present tense last April, and made a few similarly minor
tweaks.
I've got a complete rewrite of the roadmap coming along, which deals
with the larger issues of Mozilla 2.0; the future of web standards and
the "open web" vs. emerging closed, single-vendor systems; and other big
important stuff. It should be up before the end of the month.
/be
MMC Monster
[...]
> I've got a complete rewrite of the roadmap coming along, which deals
> with the larger issues of Mozilla 2.0; the future of web standards and
> the "open web" vs. emerging closed, single-vendor systems; and other big
> important stuff. It should be up before the end of the month.
Not to be a nag about it, but any update? Month's almost over. ;-)
Benedikt Kantus (formerly bkantus@web.de)
It IS already updated.
--
Benedikt Kantus
on a Thumperbunny nightly
Andrew Schultz
Where do you see anything about Mozilla 2.0 or anything else he mentioned he
would add?
--
------------------------------------------------------------------
Andrew Schultz | The views expressed might
ajsc...@eos.ncsu.edu | not represent those of NCSU.
http://www4.ncsu.edu/~ajschult/ | They are however, correct.
Benedikt Kantus (formerly bkantus@web.de)
> Benedikt Kantus (formerly bka...@web.de) wrote:
>> On 2004-02-01 00:08, MMC Monster wrote:
>>
>>
>>>Brendan Eich wrote:
>>>[...]
>>>
>>>>I've got a complete rewrite of the roadmap coming along, which deals
>>>>with the larger issues of Mozilla 2.0; the future of web standards and
>>>>the "open web" vs. emerging closed, single-vendor systems; and other big
>>>>important stuff. It should be up before the end of the month.
>>>
>>>Not to be a nag about it, but any update? Month's almost over. ;-)
>>
>>
>> It IS already updated.
>
> Where do you see anything about Mozilla 2.0 or anything else he mentioned he
> would add?
>
Ok, I admit I didn't read the original post carefully enough ;-) It is
_not_ updated, indeed.
-Bene
Axel Hecht
<...>
> I've got a complete rewrite of the roadmap coming along, which deals
> with the larger issues of Mozilla 2.0; the future of web standards and
> the "open web" vs. emerging closed, single-vendor systems; and other big
> important stuff. It should be up before the end of the month.
>
> /be
How far is this? We gonna have a few discussions on the european Mozilla
meeting feb 21, 22, and I was hoping that we could provide some
de-noised feedback on the 2.0 document from that discussion.
Axel
Brendan Eich
Sorry, lots of stuff brewing, including some things I can't talk about yet.
Here's what I'll do: instead of a big new roadmap landing, I'm going to
start blogging about 2.0 and the roadmap at
http://weblogs.mozillazine.org/roadmap/. I'll have a first entry up by
the end of this week, tomorrow ideally, and go from there. With any
luck, in a week or two I'll be able to talk about some of the cool stuff
that's brewing, too.
/be
Michael Lefevre
[snip]
> Sorry, lots of stuff brewing, including some things I can't talk about
> yet.
>
> Here's what I'll do: instead of a big new roadmap landing, I'm going to
> start blogging about 2.0 and the roadmap at
> http://weblogs.mozillazine.org/roadmap/. I'll have a first entry up by
> the end of this week, tomorrow ideally, and go from there. With any
> luck, in a week or two I'll be able to talk about some of the cool stuff
> that's brewing, too.
and then on 2004-03-10:
> I'll (finally) be blogging about them in detail at
> http://weblogs.mozillazine.org/roadmap/.
There was apparently a draft of a new roadmap kicking around 6 months ago,
then it was going to happen around the end of the year, then in February
we have "end of this week" and on the document itself "early in 2004". And
here we are moving into April and still nothing...
The current roadmap mentions that 1.0 is almost a year old and it's time
to move towards a new, stable 1.4 branch. Now apparently we may be
retiring the 1.4 branch in favour of a stable branch based on 1.7!
It'd be nice to know that mozilla.org does actually have some kind of plan
that goes beyond the next 6 weeks... If Firefox is going to be the
primary platform and reach 1.0 on the branch, and other products are being
based off the 1.7 branch, is anyone actually going to be using/testing
Seamonkey 1.8a/b/final?
--
Michael
Christian Biesinger
> is anyone actually going to be using/testing
> Seamonkey 1.8a/b/final?
Well, sure, the same people who are using seamonkey currently are likely
to use 1.8a/b/f, no?
Mooquackwooftweetmeow
> Here's what I'll do: instead of a big new roadmap landing, I'm going to
> start blogging about 2.0 and the roadmap at
> http://weblogs.mozillazine.org/roadmap/. I'll have a first entry up by
> the end of this week, tomorrow ideally, and go from there. With any
> luck, in a week or two I'll be able to talk about some of the cool stuff
> that's brewing, too.
Has the roadmap weblog been cancelled now?
-- Greg “The Twaddle” Nicholson