SeaMonkey progress?
Tsahi Asher
--
Tsahi Asher
Hebrew L10n Team
http://www.mozilla.org.il
Tobias Fischer
> is there any progress on SeaMonkey? will a 1.0 be released?
Yes. Robert Kaiser (KaiRo), Member of SeaMonkey-Council, has told in
<4374c16f$0$25098$7972...@newsreader.inode.at> (sorry, the post is in
german), that they are waiting to land the new Artwork for Branding
(probably the next two or three weeks) and than go ahead for SeaMonkey
1.0-Beta-Release something about a period of another one or two weeks
for QA.
After this Beta-Release, there was hope to get out the SeaMonkey-Final
as a Christmas-Gift.
For testing you can get the actuall 1.0b-Nighly-Builds from:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/
And sure, we need a lot of testing to get out the Beta and later the
Final Release.
Tobias
--
Nichttesten löst auch keine Probleme.
us...@domain.invalid
> On 2005-11-16 22:49, Tsahi Asher wrote:
>> is there any progress on SeaMonkey? will a 1.0 be released?
>
> Yes. Robert Kaiser (KaiRo), Member of SeaMonkey-Council, has told in
> <4374c16f$0$25098$7972...@newsreader.inode.at> (sorry, the post is in
> german), that they are waiting to land the new Artwork for Branding
> (probably the next two or three weeks) and than go ahead for SeaMonkey
> 1.0-Beta-Release something about a period of another one or two weeks
> for QA.
>
> After this Beta-Release, there was hope to get out the SeaMonkey-Final
> as a Christmas-Gift.
>
> For testing you can get the actuall 1.0b-Nighly-Builds from:
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/
>
What are the versions is this directory?
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
Juhani Tenhunen
But what is the difference between 1.5 a and 1.0 b latest trunks, actually?
Regards,
Juhani Tenhunen
Helsinki, Finland (using Sm 1.5a 2005111609)
Giacomo Magnini
> But what is the difference between 1.5 a and 1.0 b latest trunks, actually?
1.0b and later are based on Gecko 1.8 (rendering engine), stable branch.
1.5/nightly/trunk are based on Gecko 1.9.
Cheers, Giacomo.
Robert Kaiser
To say it more clearly:
SeaMonkey 1.0b (Beta) nightlies are based on the quite stable Gecko 1.8,
which is very near a final release itself (presumably in a from packed
with Firefox 1.5 final). This code should not see very big changes, only
bug fixes, at the moment (though a SeaMonkey 1.1 might get based on this
code later on).
SeaMonkey 1.5a (Alpha) nightlies are from the so-called "trunk", which
is the current unstable development code, based on Gecko 1.9a1 nightly
code, which is also unstable devlopment code. Additionally, the
SeaMonkey-specific code on that "trunk" will see quite a few big changes
on the code level within the next weeks and months to come.
Note that all "nightly" code always bares the version number of the
upcoming release planned to come off that code. So when you read "Gecko
1.9a1 nightly" this means that this is some code point on the way to a
Gecko 1.9 Alpha 1 release, but this is not actually the release code
itself (yet). Same with "SeaMonkey 1.5a nightly" or "SeaMonkey 1.0b
nightly" or whatever.
Robert Kaiser
Robert Kaiser
> is there any progress on SeaMonkey? will a 1.0 be released?
Yes.
Our current plan is to get outstanding bugs marked
"blocking-seamonkey1.0b+" fixed, the main of it being the new artwotrked
introduced along with our new logo, which is to be announced soon (we
have decided on it, and are currently preparing all imagery needed to
make builds with it available). Then we and everybody able to help will
need to test/QA the hell out of those builds, and we hope we can release
a Beta approx. one or two weeks after the artwork is in.
SeaMonkey 1.0 Beta is planned to be feature and hopefully L10n freeze
for final, only stability, security and regression fixes should go in
after that, and we need even more hands and eyes on testing those and
following builds, so that we can release 1.0 final shortly after that
and Gecko 1.8 final are out.
If further security releases to 1.0 are needed, they might be called
1.0.x, while a seperate branch from the 1.0 codebase will be used to
develop SeaMonkey 1.1, which should contain additional feature work, but
no big restructuring. See
https://bugzilla.mozilla.org/show_bug.cgi?id=315312 for what we plan there.
On the other hand, "trunk" will see some big restructuring of code,
targeting a migration to the new toolkit (which means at least its UI
bindings and at most full XULRunner capability, the truth might lie
somewhere between those two), but also consolidating SeaMonkey-specific
code in the suite/ directory of the mozilla.org source tree and making
"source L10n" possible. Along with that, things like a new icon set for
the default theme ("Classic", if it'll still called that then) and new
features like the stuff from 1.1 should be seen here as well. And, not
to forget, any improvements in core/Gecko trunk code will be available
there, of course.
As you see, lots of stuff lies ahead of us, and the project is not dead
at all yet :)
Robert Kaiser
P.S.: I just realized it may be a good idea to post this in the
SeaMonkey blog at http://weblogs.mozillazine.org/seamonkey/ as well...
Maybe I should look into that :)
Ricardo Palomares Martinez
> Tsahi Asher schrieb:
>> is there any progress on SeaMonkey? will a 1.0 be released?
>
> Yes.
>
> Our current plan is to get outstanding bugs marked
> "blocking-seamonkey1.0b+" fixed, the main of it being the new artwotrked
> introduced along with our new logo, which is to be announced soon (we
> have decided on it, and are currently preparing all imagery needed to
> make builds with it available). Then we and everybody able to help will
> need to test/QA the hell out of those builds,
FWIW, I've been using SeaMonkey 1.0alpha as my production environment
since it was oficially released, and I haven't experienced stability
problems AFAICT. In fact, the only annoyances I /suffer/ by using
SeaMonkey 1.0alfa is that some extensions are not (yet) working in it
(namely, Calendar and TagZilla).
>
> P.S.: I just realized it may be a good idea to post this in the
> SeaMonkey blog at http://weblogs.mozillazine.org/seamonkey/ as well...
> Maybe I should look into that :)
Nice to know that such a weblog exists... :-)
Regards.
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Philip Chee
> FWIW, I've been using SeaMonkey 1.0alpha as my production environment
> since it was oficially released, and I haven't experienced stability
> problems AFAICT. In fact, the only annoyances I /suffer/ by using
> SeaMonkey 1.0alfa is that some extensions are not (yet) working in it
> (namely, Calendar and TagZilla).
?? I don't know about Calendar, but Tagzilla is working here with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051024
SeaMonkey/1.1a
It does pop up an additional window after sending off a message that I have
to close but I can live with that.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]Windows may be slow, but at least it takes up a lot of room
* TagZilla 0.059
Rinaldi J. Montessi
===
> FWIW, I've been using SeaMonkey 1.0alpha as my production environment
> since it was oficially released, and I haven't experienced stability
> problems AFAICT. In fact, the only annoyances I /suffer/ by using
> SeaMonkey 1.0alfa is that some extensions are not (yet) working in it
> (namely, Calendar and TagZilla).
Calendar is a build time option:
./.mozconfig:mk_add_options MOZ_CO_PROJECT=suite,calendar
./.mozconfig:ac_add_options --enable-calendar
Rinaldi
--
He had occasional flashes of silence that made his conversation
perfectly delightful.
-- Sydney Smith
Adrian (Adrianer) Kalla
> FWIW, I've been using SeaMonkey 1.0alpha as my production environment
> since it was oficially released, and I haven't experienced stability
> problems AFAICT. In fact, the only annoyances I /suffer/ by using
> SeaMonkey 1.0alfa is that some extensions are not (yet) working in it
> (namely, Calendar and TagZilla).
>
Calendar works in SeaMonkey, but you must compile an own SM build with
Calendar enabled ;)
Adrianer
Ricardo Palomares Martinez
>
> ?? I don't know about Calendar, but Tagzilla is working here with:
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051024
> SeaMonkey/1.1a
>
> It does pop up an additional window after sending off a message that I have
> to close but I can live with that.
Err... My experience is the same that the one reported in this bug:
http://bugzilla.mozdev.org/show_bug.cgi?id=11147
I can live with it, too, but it would be better if the bug get fixed.
Ricardo Palomares Martinez
>
> Calendar is a build time option:
>
> ./.mozconfig:mk_add_options MOZ_CO_PROJECT=suite,calendar
> ./.mozconfig:ac_add_options --enable-calendar
>
Yes, I know it, but I don't know how to compile SeaMonkey itself, so
I'd rather wait till a Calendar XPI is available. ;-)
Tobias Fischer
[...]
> One more explanation, please. What is the difference between versions
> available at
>
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/ and
>
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/ ?
The Builds available here are both built from Trunk, so they have the
Gecko 1.9a1 Revision.
The difference was that the Builds are made original from MoFo are
uploaded into the first named location, the Builds uploaded from
third-party-volunteers are going into ../contrib.
>
> I assume
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/
> is just a compilation of the latest versions available (from the dirs just
> above it) for each OS. (?)
Hmm. No, these are Gecko 1.8-Branch-Builds for Testing and have the
Release of SeaMonkey 1.0 not to far away.
Because there are currently no Tinderboxen from the MoFo available that
builds Gecko 1.8-Branch-Builds for SeaMonkey (hopefully someone can set
up some, so we can get Talkback-Enabled-Builds again. Chase?) some
People from and/or associated with SeaMonkey-Council compile the
uploaded Builds.
And like all the Third-Party-Builds they land in ../contrib
Tobias
Christian Biesinger
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/ and
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/ ?
The former contains builds made by mozilla.org; the latter contains
builds from other contributors. (Looks like it only contains OS/2 on trunk)
> I assume
> ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/
> is just a compilation of the latest versions available (from the dirs just
> above it) for each OS. (?)
That's correct.
Philip Chee
> Err... My experience is the same that the one reported in this bug:
> http://bugzilla.mozdev.org/show_bug.cgi?id=11147
> I can live with it, too, but it would be better if the bug get fixed.
Ah, I don't use automatic tagline insertion. I like to check what Tagzilla
is going to insert.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]FATAL SYSTEM ERROR: Press F13 to continue...
* TagZilla 0.059
Adrian (Adrianer) Kalla
> Yes, I know it, but I don't know how to compile SeaMonkey itself, so
> I'd rather wait till a Calendar XPI is available. ;-)
>
>
you can try Calendar from my build:
http://beta.aviary.pl/adrianer/calendar-20051004.xpi
P.S. I have written a script for Win32 that automaticly downloads the
latest cvs, builds the source, builds the installers and etc. ;)
Melchert Fruitema
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1)
Gecko/20051117 SeaMonkey/1.5a
Regards, Mel
Ricardo Palomares Martinez
I'm afraid I'm using Linux at home. :-)
No problem, I still have faith in that non-working Calendar XPIs in
SeaMonkey won't probably work in Fx & Tb 1.5 either, so we won't have
to wait forever. :-)
Lewis Rosenthal
I wish you had a calendar build for OS/2, Adrian... :-(
--
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA, CLE
Rosenthal & Rosenthal, LLC
Accountants / Network Consultants
New York / Northern Virginia www.2rosenthals.com
eComStation Consultants www.ecomstation.com
Novell Users International www.novell.com/linux/truth
Need a managed Wi-Fi hotspot? www.hautspot.com
------------------------------------------------------------
Stegozor
> Tsahi Asher schrieb:
>> is there any progress on SeaMonkey? will a 1.0 be released?
>
> P.S.: I just realized it may be a good idea to post this in the
> SeaMonkey blog at http://weblogs.mozillazine.org/seamonkey/ as well...
Refreshing news, thanks. Like Tsahi, I was wondering if Seamonkey was
still alive. I know the most important thing is the code, but perhaps
you should give more information about Seamonkey progress on
http://www.mozilla.org/projects/seamonkey , which seems to be the main
page about my favourite browser, and on the wiki. If you do so, you will
prevent end users like me from polluting developer newsgroups. ;)
I'm going to bookmark the blog...