[As we have no litmus results yet, sending to support and QA groups as
well.]
Robert Kaiser wrote:
Hi all,
For one last time, I tagged a CVS tree for a SeaMonkey 1.x release, and
for one lat time, I made my to-be-retired old tinderbox machines spin
release candidate builds.
We will be releasing SeaMonkey 1.1.19, with the same base as Thunderbird
2.0.0.24, without a lot of actual release fanfare, actually, the big
announcement will be the end of the line for SeaMonkey 1.x, that there
is one last release will not be much more than a remark in that
announcement that is to be made as soon as we have some useful testing
and Thunderbird is ready to push their release as well.
A number of security and stability fixes went into this release, see
<https://bugzilla.mozilla.org/buglist.cgi?keywords_type=anywords&keywords=fixed-seamonkey1.1.19%2Cfixed1.8.1.24%2Cverified1.8.1.24&product=Core&product=MailNews+Core&product=SeaMonkey&product=Other+Applications>,
we need good testing of the candidate builds to avoid regressions if
possible. Not all security problems with 1.8.1.x browser code have been
fixed though, from what I'm told - still this is better to leave those
people stuck with 1.x than the previous 1.1.18 release.
Please help testing our SeaMonkey 1.1.19 candidate builds
<http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.19/>
- preferably via performing the smoketests from the, please go to and do
a SeaMonkey 1.1 test run
<http://litmus.mozilla.org/run_tests.cgi?test_run_id=11> on
<http://litmus.mozilla.org/>.
Once we have verified that the builds work well, we can announce the
SeaMonkey 1.x end of life and release this last security-enhanced
version to our remaining 1.x users.
Thanks for your help,
Robert Kaiser
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
