Dropping 1.9.2, Going 1.9.3 for SeaMonkey 2.1

[re-post of 
http://home.kairo.at/blog/2010-02/dropping_1_9_2_going_1_9_3_for_seamonkey 
here in the groups/lists]

I blogged on SeaMonkey 2.1 planning earlier in 
http://home.kairo.at/blog/2010-01/seamonkey_2_1_planning and also about 
the fact that we have been unsure if we should go 1.9.2 or 1.9.3 in 
terms of the platform there.

I sent mails to the SeaMonkey Council and a few quite active developers 
in the last days, and asked for opinions on dropping support for 1.9.2 
and going for firmly basing SeaMonkey 2.1 on Mozilla platform 1.9.3 instead.

Nobody was really against that, and most people were firmly or mostly 
supportive, so that we decided to go for this.

With this, the suite directory and application on comm-central will only 
support 1.9.3 from now on, and SeaMonkey will not support 1.9.2 at all.

We will be erroring out for --enable-application=suite builds when a 
Mozilla 1.9.2 tree is in use (bug 546484), and also remove 1.9.2 ifdefs 
from the suite/ directory in comm-central (bug 546487).

This only affects SeaMonkey-specific code, of course, and Thunderbird 
will be going for 1.9.2 as main target from the same comm-central tree, 
so any shared code needs ifdefs to deal with 1.9.2 vs. 1.9.3 until we 
branch comm-1.9.2 some time in the future (bug 544237).

We hope we can work towards a good SeaMonkey 2.1 release with 
improvements in features and be able to close the gap to Firefox by 
releasing closer to their next final release. Scheduling for both those 
releases is still a bit unsure, but we'll see more about that once we 
get a clearer picture of what features we can get in and what state 
we're in for delivering something stable to users (that's true for both 
Firefox and SeaMonkey).

Robert Kaiser
0
Robert
2/16/2010 9:02:00 PM
mozilla.dev.apps.thunderbird 3439 articles. 0 followers. Post Follow

7 Replies
621 Views

Similar Articles

[PageSpeed] 16

On 2010-02-16, at 4:02 PM, Robert Kaiser wrote:

> I sent mails to the SeaMonkey Council and a few quite active =
developers in the last days, and asked for opinions on dropping support =
for 1.9.2 and going for firmly basing SeaMonkey 2.1 on Mozilla platform =
1.9.3 instead.

That's great news, and I think it'll be best for everyone in terms of =
focusing all the Mozilla platform related development on the same =
target.

At the same time, I hope the SeaMonkey Council (great mental image!) =
understands that, as of this time, there's no roadmap for when Mozilla =
1.9.3 will be finalized. My gut feeling is late 2010, but there's still =
a bunch of work to be done before I can give a date in which I have a =
strong degree of confidence.

cheers,
mike=
0
Mike
2/16/2010 9:08:42 PM
Mike Beltzner wrote:
> On 2010-02-16, at 4:02 PM, Robert Kaiser wrote:
>
>> I sent mails to the SeaMonkey Council and a few quite active developers in the last days, and asked for opinions on dropping support for 1.9.2 and going for firmly basing SeaMonkey 2.1 on Mozilla platform 1.9.3 instead.
>
> That's great news, and I think it'll be best for everyone in terms of focusing all the Mozilla platform related development on the same target.

I agree, and especially as we are trying to team up with the KompoZer 
project to get editor/Composer beefed up again, we might want to get 
something into the platform that helps that project as well, which of 
course is better to do for 1.9.3 than for an already stable release.

> At the same time, I hope the SeaMonkey Council (great mental image!) understands that, as of this time, there's no roadmap for when Mozilla 1.9.3 will be finalized. My gut feeling is late 2010, but there's still a bunch of work to be done before I can give a date in which I have a strong degree of confidence.

We are aware of that, and that's the main reason why it took as somewhat 
longer than expected to come to a decision here, but I think a fall 
release would match us fine, actually.

Robert Kaiser
0
Robert
2/16/2010 9:22:38 PM
On 02/16/2010 01:02 PM, Robert Kaiser wrote:
> [re-post of 
> http://home.kairo.at/blog/2010-02/dropping_1_9_2_going_1_9_3_for_seamonkey 
> here in the groups/lists]
> 
> I blogged on SeaMonkey 2.1 planning earlier in 
> http://home.kairo.at/blog/2010-01/seamonkey_2_1_planning and also about 
> the fact that we have been unsure if we should go 1.9.2 or 1.9.3 in 
> terms of the platform there.
> 
> I sent mails to the SeaMonkey Council and a few quite active developers 
> in the last days, and asked for opinions on dropping support for 1.9.2 
> and going for firmly basing SeaMonkey 2.1 on Mozilla platform 1.9.3 instead.
> 
> Nobody was really against that, and most people were firmly or mostly 
> supportive, so that we decided to go for this.
> 
> With this, the suite directory and application on comm-central will only 
> support 1.9.3 from now on, and SeaMonkey will not support 1.9.2 at all.
> 
> We will be erroring out for --enable-application=suite builds when a 
> Mozilla 1.9.2 tree is in use (bug 546484), and also remove 1.9.2 ifdefs 
> from the suite/ directory in comm-central (bug 546487).
> 
> This only affects SeaMonkey-specific code, of course, and Thunderbird 
> will be going for 1.9.2 as main target from the same comm-central tree, 
> so any shared code needs ifdefs to deal with 1.9.2 vs. 1.9.3 until we 
> branch comm-1.9.2 some time in the future (bug 544237).

Been away for a few weeks, so trying to catch up now... What issues will
this have w/lightning which finally is starting to sync well with
SeaMonkey? See:

<http://weblogs.mozillazine.org/calendar/2010/02/lightning_builds_move_towards.html>


0
NoOp
3/3/2010 10:15:40 PM
NoOp wrote:

>Been away for a few weeks, so trying to catch up now... What issues will
>this have w/lightning which finally is starting to sync well with
>SeaMonkey? See:
>
><http://weblogs.mozillazine.org/calendar/2010/02/lightning_builds_move_towards.html>

What it basically means is that you should not expect Lightning nightlies
and SeaMonkey nightlies to play along very well.

You should also not expect Lightning 1.0 beta2 to support SeaMonkey.

Cya
Simon
-- 
Calendar Localisation (L10n) Coordinator
Calendar website maintainer: http://www.calendar-project.org
Calendar developer blog:     http://weblogs.mozillazine.org/calendar
0
Simon
3/4/2010 12:33:20 AM
NoOp wrote:
> What issues will
> this have w/lightning which finally is starting to sync well with
> SeaMonkey?

We still need to work out the details of that, we hope to get something 
that works for both our teams there.

Robert Kaiser
0
Robert
3/4/2010 1:00:38 AM
On 03/03/2010 05:00 PM, Robert Kaiser wrote:
> NoOp wrote:
>> What issues will
>> this have w/lightning which finally is starting to sync well with
>> SeaMonkey?
> 
> We still need to work out the details of that, we hope to get something 
> that works for both our teams there.
> 
> Robert Kaiser

Well, hopefully you can get it sorted out with Simon Paquet as I'd hate
to see lightning support get dropped/borked after it's finally working
well with SM 2.0.


0
NoOp
3/4/2010 2:01:10 AM
NoOp wrote:
> Well, hopefully you can get it sorted out with Simon Paquet as I'd hate
> to see lightning support get dropped/borked after it's finally working
> well with SM 2.0.

Same here. It's mostly a question of (human) resources, I guess - and 
whatever trickery else is needed, but technical concerns can usually be 
solved. ;-)

Robert Kaiser
0
Robert
3/4/2010 2:55:56 AM
Reply:

Similar Artilces:

SeaMonkey 2.1
An increasing number of features are diverging between Gecko 1.9.2 and Gecko 1.9.3; this gives us a number of options, with pros and cons for each, but please don't consider this an exhaustive list. 1. Stick with 1.9.2 for now, don't use 1.9.3 features at all * Pro: We know what features we have to port * Con: Lots of catching up on trunk after comm-central forks/after releasing 2.1 2. Write code using feature detection for 1.9.3/backward compatibility for 1.9.2 * Pro: More flexible than any other option * Co...

selecting ? selecting of 1., 2. , 3., 4., 5., 6. is slow (1-3 second) then selecting of 7.,8.,9. go on is so fast (0.1 second or more fast).. how can i get fast for selecting of 1., 2. , 3., 4., 5., 6
hello friends selecting of 1., 2. , 3., 4.(sometime even 5., 6.) is slow (1-3 second) then selecting of 7.,8.,9.(sometimes 5., 6.,) go on is so fast (0.1 second or more fast).. how can i get fast for selecting of 1., 2. , 3., 4., 5., 6. is slow ?? recordcount is almost 1.050.000.. i do selecting 1.2.3. go on same page with treeview1.. treeview1 in masterpage.master.. gridview1 and datasource1 are in pagelist.aspx (it connets datasource1)..productnumber is primarykey for index.. kategori, kategori1 and kategori2, price, datemin are index from keys/index in table1 (right clicking menu)....

From 2.1.2 to 3.1 or 2.1.2 to 3.0.13 to 3.1
I'm checking back in after being away for a couple of months and I missed the 3.1 release. I can't seem to find any info on what's new in 3.1 and also what the upgrade path should be. So, is the recommended path for upgrading from v 2.1.2 to go directly to 3.1 or do I need to go to 3.0.13 first? Are there any big issues in 3.1 that make it a "gotta have it" version?I did a couple of 2.1.2 to 3.0.12 upgrades but haven't upgraded to or tested 3.1 yet. I have one 2.1.2 site that is commercial and I need it to be down as little time as possible. It also has a lot of third party modules...

Thoughs on 1.9, 1.9.1, and 2
One of the common discussions that seems to come up often is what happens when 1.9 is done: do we go full-bore on 2? Do we plan for an interim release? Do we have a way of fixing small polish/regression bugs that we weren't able to get to 1.9 before the next major release? The main thing I'll assert here is that I think it is vitally important that the entire engineering team commits fully to work that will benefit whatever initial release "Mozilla 2" becomes: being able to make API-breaking changes, architectural improvements, potentially doing some of the large ...

Important App Update changes on the 1.9.1 and 1.9.2 branches
The value for the %BUILD_TARGET% parameter of the app.update.url preference is changing for Mac OS X Universal builds on the Mozilla 1.9.1 and 1.9.2 stable branches and should land for 1.9.2.12 and 1.9.1.15 releases unless an unforeseen issue comes up. Previously the value was always Darwin_Universal-gcc3 which doesn't distinguish which architecture the application is running on. The value will be Darwin_ppc-gcc3-u-ppc-i386 for Universal builds using the PPC architecture and Darwin_x86-gcc3-u-ppc-i386 for Universal builds using the i386 architecture. This is necessary to d...

Merging of 1.9.1 to 1.9.2 done
Hi all, I just finished merging a whole ton of locales from 1.9.1 via l10n-central to 1.9.2. I only touched those locales that didn't work on central nor 1.9.2 outside of 1.9.1. That is, if there were commits on central, I usually didn't merge that over. If you think that you can benefit from getting 1.9.1 content over, get in touch with me or someone else from the l10n-drivers team and we'll try to help you with more attention to detail. In particular, we'd need to know what of central to keep, and what of 1.9.1 to use. HTH Axel ...

SeaMonkey 1.1.18 vs SeaMonkey 2.1 (if/when 2.1 is released)
I will clearly state that I am not a computer whiz...thus, I have a number of concerns regarding SeaMonkey 2.0 installation on my system. I have been reading the many SeaMonkey 2.0 messages on this newsgroup with some concern about my ability to fix the problems that could occur with the installation of 2.0. It seems that the move from 1.1.18 to 2.0 is not happening without a number of glitches along the way. Thus, in light of what I have read, I am wondering if it would wise for me to wait for a future release of SeaMonkey before upgrading my system...I suppose I am hoping tha...

1.9.1 and 1.9.2 unit tests on minis
Hi, I have enabled unit tests on the minis for the Fedora and OSX machines (only 32-bit plaforms)[1]. Once I see enough activity I will be disabling them from running on the builders side [2]. As we improve our infrastructure we will enable more and more branches and disabling more and more of them from the builders side and therefore reduce the load on that side. Let me know if you have any questions, Armen [1] https://bugzilla.mozilla.org/show_bug.cgi?id=573480 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=557918 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Are...

examples of l10n updates on 1.9.1, 1.9.2
Hi there, following up on the discussion on the delivery call, here's a list of changes that I think we should take as minor updates. They're a bit more content-ish on 1.9.2 thanks to lorentz strings. I hope the links make it allright, there should be one per line, 8 for 3.5 and 12 for 3.6. A bit on reading those diffs: It only offers rich content for things it knows about. I.e., not for dictionaries or README.txt. For dictionaries, that's a feature because those diffs are huge quite often. README.txt wasn't important enough so far for me to hook up revisi...

SeaMonkey 1.0.9 and 1.1.2 he-IL
hi, now that i have a job, i have very little time left for the l10n work. so these came out a little later than they should have. 1.1.2 ~~~~~ win32: http://downloads.sourceforge.net/hebmoz/seamonkey-1.1.2.he-IL.win32.installer.exe language pack: http://downloads.sourceforge.net/hebmoz/seamonkey-1.1.2.he-IL.langpack.xpi 1.0.9 ~~~~~ win32: http://downloads.sourceforge.net/hebmoz/seamonkey-1.0.9.he-IL.win32.installer.exe language pack: http://downloads.sourceforge.net/hebmoz/seamonkey-1.0.9.he-IL.langpack.xpi the language packs should be used with their respective RTL t...

SeaMonkey 1.0.9 and 1.1.2 in italian
Hi everyone, since kairo said we can start making builds based on the latest candidates, here there are the italian ones. If there'll be problem with the candidates, i'll make them again. 1.1.2: Installer: http://downloads.sourceforge.net/mozilla-italia/seamonkey-1.1.2.it-IT.win32.installer.exe Langpack: http://downloads.sourceforge.net/mozilla-italia/seamonkey-1.1.2.it-IT.langpack.xpi Zip: http://downloads.sourceforge.net/mozilla-italia/seamonkey-1.1.2.it-IT.win32.zip 1.0.9: Installer: http://downloads.sourceforge.net/mozilla-italia/seamonkey-1.0.9.it-IT.win32.i...

SeaMonkey 1.0.9 and 1.1.2 upcoming
Hi localizers, I'd like to give you a notice of our upcoming SeaMonkey 1.0.9 and 1.1.2 releases. Both are planned to go public in sync with the Firefox updates currently scheduled for next week, see their schedule at http://wiki.mozilla.org/Firefox:1.5.0.12-2.0.0.4 Our candidate builds for those releases are here: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.0.9/ http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.2/ From QA up till now, we believe that builds in those directories are ready to go final unchanged, so you shou...

SeaMonkey 1.1.2/1.0.9 soon?
MoCo will release Firefox 2.0.0.3/1.5.0.11 soon: http://developer.mozilla.org/devnews/index.php/2007/03/04/firefox-2003-and-2004/ Are there any plans to have a SM 1.1.2/1.0.9 at the same time? -- Adrian Kalla Adrian (Adrianer) Kalla schrieb: > MoCo will release Firefox 2.0.0.3/1.5.0.11 soon: > http://developer.mozilla.org/devnews/index.php/2007/03/04/firefox-2003-and-2004/ > > Are there any plans to have a SM 1.1.2/1.0.9 at the same time? Not yet. We are looking closely at what patches will be included there, but I currently see no immediate reason why we need t...

Heads up, the next Firefox 3.6.x platform version is 1.9.2.6 instead of 1.9.2.5
It was suggested in a bug I mention this to the list... Firefox 3.6.4 has a platform version of 1.9.2.4. The version number = 1.9.2.5 is currently being used by Fennec. We=92ll be taking fixes above = and beyond that version, so the next platform version Firefox will use = will be named 1.9.2.6. We will keep the version numbers coherent by = naming it Firefox 3.6.6 (essentially skipping over 3.6.5). I will be moving the blocking flags and status flags as appropriate, so = if you see activity in bugs don=92t worry. Also, If you have approvals = for 1.9.2.5 they are now for 1.9.2.6 (...

Web resources about - Dropping 1.9.2, Going 1.9.3 for SeaMonkey 2.1 - mozilla.dev.apps.thunderbird

The Hawaiian Seamonkey
Diving, eating, gardening, loving the Big Island of Hawaii

The SeaMonkey® Project
The SeaMonkey project is a community effort to develop the SeaMonkeyall-in-one internet application suite (see below).Such a software suite was ...

SeaMonkey - Wikipedia, the free encyclopedia
cross-platform Internet suite . It is the continuation of the former Mozilla Application Suite , based on the same source code. Core Mozilla ...

Review: SeaMonkey 1.1.8 for the Mac
SeaMonkey 1.1.8, the Mozilla Foundation's all-in-one Internet application, combines browsing, e-mail, HTML editing, and IRC chat.

SeaMonkey 2.3 Beta 1 arrives for testing
Based on the same Gecko browser engine as Firefox 6, SeaMonkey 2.3 Beta 1 has been released for testing. It offers improvements to WebGL that ...

SeaMonkey Offers Browser, E-Mail, and Chat
... resuscitated a group of Internet tools built by Netscapewhose spin-off, Mozilla, brought out the popular Firefox Web browser. Renamed SeaMonkey ...

SeaMonkey, Mozilla's all-in-one Internet suite, releases new beta
The SeaMonkey Project has released SeaMonkey 2.1 Beta 3 , a version that makes a lot of new functionality available to a wide audience for the ...

SeaMonkey review
Browse the web, work with mail, chat in IRC and edit HTML

SeaMonkey 2.33
... advanced e-mail, newsgroup and feed client, IRC chat, and HTML editing made simple, all your Internet needs in one application. The SeaMonkey ...

Seamonkey 1.1 Released
stuuf writes "Version 1.1 of the Seamonkey Internet Application Suite is now available, with quite a few improvements over the 1.0 series. Some ...

Resources last updated: 12/18/2015 5:56:33 AM