ANNOUNCE: SeaMonkey 2.18 - Where are you?

Justin Wood (Callek)

unread,

May 14, 2013, 6:41:09 PM5/14/13

to

Hey Everyone

So SeaMonkey 2.18 was supposed to be out today, so where is it?

We have had a hardware error in the systems that allow us to reliably
generate the release — Without these systems anything we create will be
of unknown quality/stability.

In order to meet our own quality and stability requirements we are NOT
releasing SeaMonkey 2.18.

While there is a chance we could have these systems back up in time to
do an intermediate release (say something corresponding to a possible
Gecko 21.0.1) we can not promise nor plan for it at this time.

We are actively working on repairing the system and its data, once that
is complete we will go forth with a new BETA based on the SeaMonkey 2.19
train, and we expect to release SeaMonkey 2.19 on time, on June 25′th.

We thank you for your understanding.

--
~Justin Wood (Callek)

Heinz W. Simoneit

unread,

May 15, 2013, 4:13:19 AM5/15/13

to dev-apps-...@lists.mozilla.org

Hi,

what about 2.18b4? Do you recommend not to run it?

cu
Heinz

--
Have a nice time!

Frank Wein

unread,

May 15, 2013, 1:01:19 PM5/15/13

to

Heinz W. Simoneit wrote:
> what about 2.18b4? Do you recommend not to run it?
>
> cu
> Heinz

Beta versions usually still have bugs. You can use it, but we don't want
to distribute a beta build as final build to users.

Frank

Iacopo Benesperi

unread,

May 15, 2013, 1:22:18 PM5/15/13

to

Justin Wood (Callek) ha scritto:

> In order to meet our own quality and stability requirements we are NOT
> releasing SeaMonkey 2.18.

Are you going to at least release a compressed file with the sources? Or
are they affected by this problem, too?

Iacopo

P.S. sorry in advance if it's considered cross-posting

Jens Hatlak

unread,

May 15, 2013, 3:58:18 PM5/15/13

to

Iacopo Benesperi wrote:
> Are you going to at least release a compressed file with the sources? Or
> are they affected by this problem, too?

I don't think so. Providing sources would imply tagging SM 2.18 which I
don't think will happen. The closest you could get right now would
probably be pulling tag RELEASE_21_END from comm-release and
FIREFOX_21_0_RELEASE from mozilla-release.

Compared to 2.18b4, the only additional SM-specific changes are:
* The new mail alert has been disabled for now since it could behave
incorrectly (pref: mail.biff.show_new_alert) (bug 840474)
* The Geolocation prompt no longer offers an action in Private Browsing
mode if the action remembered permissions for more than a session
(bug 870728)

HTH

Jens

--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>

Neil

unread,

May 15, 2013, 6:43:03 PM5/15/13

to

Jens Hatlak wrote:

> Iacopo Benesperi wrote:
>
>> Are you going to at least release a compressed file with the sources?
>> Or are they affected by this problem, too?
>
> I don't think so. Providing sources would imply tagging SM 2.18 which
> I don't think will happen. The closest you could get right now would
> probably be pulling tag RELEASE_21_END from comm-release and
> FIREFOX_21_0_RELEASE from mozilla-release.
>
> Compared to 2.18b4, the only additional SM-specific changes are:
> * The new mail alert has been disabled for now since it could behave
> incorrectly (pref: mail.biff.show_new_alert) (bug 840474)
> * The Geolocation prompt no longer offers an action in Private
> Browsing mode if the action remembered permissions for more than a
> session (bug 870728)

Other fix(es) would have landed had the trees been open...

--
Warning: May contain traces of nuts.