2010-02-16 23:10
<< Weekly Status Report, W06/2010 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Dropping 1.9.2, Going 1.9.3 for SeaMonkey 2.1
I reported on SeaMonkey 2.1 planning earlier 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, and also remove 1.9.2 ifdefs from the suite/ directory in comm-central.
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.
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).
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, and also remove 1.9.2 ifdefs from the suite/ directory in comm-central.
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.
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).
Entry written by KaiRo and posted on February 16th, 2010 21:55 | Tags: Mozilla, SeaMonkey, SeaMonkey 2.1 | 6 comments
TrackBack/Pingback
Comments