Comments on: More Seamonkey fun (comments from the peanut gallery) http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/ Fun and games with the politics of open source Tue, 28 Sep 2010 20:03:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: OstGote http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/comment-page-1/#comment-531 OstGote Thu, 10 Mar 2005 07:58:57 +0000 http://www.steelgryphon.com/blog/?p=38#comment-531 If you want to support Seamonkey (Mozilla Suite), look at http://wiki.mozilla.org/wiki/SeaMonkey:Home_Page and see if you can help (see supporters). Thanks. If you want to support Seamonkey (Mozilla Suite), look at http://wiki.mozilla.org/wiki/SeaMonkey:Home_Page and see if you can help (see supporters). Thanks.

]]> By: kwanbis http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/comment-page-1/#comment-530 kwanbis Wed, 09 Mar 2005 12:48:45 +0000 http://www.steelgryphon.com/blog/?p=38#comment-530 as an ex suite user, i really don't understand the need for it ... it took a while for ff/tb, but it finally catched on the suite, and is a better alternative IMHO ... having the suite, divides the already little foundation's resources even more as an ex suite user, i really don’t understand the need for it … it took a while for ff/tb, but it finally catched on the suite, and is a better alternative IMHO … having the suite, divides the already little foundation’s resources even more

]]> By: Matti http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/comment-page-1/#comment-529 Matti Wed, 09 Mar 2005 09:46:19 +0000 http://www.steelgryphon.com/blog/?p=38#comment-529 or they should deleay 1.8 until they need 1.8 for FF... or they should deleay 1.8 until they need 1.8 for FF…

]]> By: OstGote http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/comment-page-1/#comment-528 OstGote Wed, 09 Mar 2005 09:12:14 +0000 http://www.steelgryphon.com/blog/?p=38#comment-528 What for a argumentation ... Why must Mozilla 1.8 be a stable release? Mozilla 1.1,1.2, 1.3, 1.5, and 1.6 were final but not stable branch releases. Where is the problem to state that clearly? If someone has problems with 1.8, one could say him to upgrade to a current trunk release like 1.9a. What for a argumentation … Why must Mozilla 1.8 be a stable release? Mozilla 1.1,1.2, 1.3, 1.5, and 1.6 were final but not stable branch releases. Where is the problem to state that clearly? If someone has problems with 1.8, one could say him to upgrade to a current trunk release like 1.9a.

]]> By: James http://snarkfest.net/blog/2005/03/09/more-seamonkey-fun-comments-from-the-peanut-gallery/comment-page-1/#comment-527 James Wed, 09 Mar 2005 08:15:58 +0000 http://www.steelgryphon.com/blog/?p=38#comment-527 This isn't required. In the past, 1.0 and 1.4 were identified as "long-lived" stable branches for embedders and integrators to build upon, which would receive security updates for a long time. See http://web.archive.org/web/20021026081932/http://www.mozilla.org/roadmap.html and http://web.archive.org/web/20030801081914/http://www.mozilla.org/roadmap.html However, 1.1, 1.2, 1.3, 1.5, 1.6 were all released in the interim with no expectation by the community of long-term support. The Seamonkey 1.8 advocates are just asking for a return to these intermediate releases. As for QA/Certification, FFx/Tb 1.0.x and Seamonkey 1.7.x are largely similar, as MoFo is trying to keep the Gecko versions of these two in sync. Of couse, having said all this, I wouldn't object to a Mozilla Communicator 1.0 project if that's what's required for further Seamonkey releases. This isn’t required. In the past, 1.0 and 1.4 were identified as “long-lived” stable branches for embedders and integrators to build upon, which would receive security updates for a long time.
See http://web.archive.org/web/20021026081932/http://www.mozilla.org/roadmap.html and http://web.archive.org/web/20030801081914/http://www.mozilla.org/roadmap.html
However, 1.1, 1.2, 1.3, 1.5, 1.6 were all released in the interim with no expectation by the community of long-term support.
The Seamonkey 1.8 advocates are just asking for a return to these intermediate releases.

As for QA/Certification, FFx/Tb 1.0.x and Seamonkey 1.7.x are largely similar, as MoFo is trying to keep the Gecko versions of these two in sync.

Of couse, having said all this, I wouldn’t object to a Mozilla Communicator 1.0 project if that’s what’s required for further Seamonkey releases.

]]>