I just realized I forgot to send a note here, and I'm sorry for that.
In sync with Thunderbird 2.0.0.24, the SeaMonkey team is preparing for
the last security and stability release from the Mozilla 1.8 branch.
The planned shipping date for SeaMonkey 1.1.19 is today, the
announcement will be about the end of life for SeaMonkey 1.x, with
1.1.19 being an improvement to 1.1.18 but NOT fixing all known security
issues.
Our candidate builds for the new release are here:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.19/
As always, there are no locale changes, so language packs from the
SeaMonkey 1.1.x series should all still work for this release, but
localized binaries need to be repackaged.
The candidate binaries are identical to the ones we'll release, we
didn't see any unexpected problems come up in QA.
You can start creating your localized binaries from the builds linked
here - as always, please don't release those to the wide public before
we have published the original en-US versions.
Thanks to all of you who stayed with the more clumsy process we had for
the SeaMonkey 1.x series, you helped us and our shared users
tremendously in those times, and I hope we have a long-going future
together with the more modern code and processes in SeaMonkey 2 and
future releases.
Greetings,
Robert Kaiser
SeaMonkey Council member
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: ung...@mozilla-russia.org
==>Gmail Talk ID: ung...@gmail.com
==>IRC: irc://irc.mozilla.org/mozilla-ru
http://l10n.mozilla.org/~une/sm-1.1.19/
Thanks. Carlos
Thanks, uploaded to the prepared directory for the release in
preparation for going public today.
Robert Kaiser
On 2010/03/15, at 23:29, Robert Kaiser wrote:
> Hi localizers,
>
> I just realized I forgot to send a note here, and I'm sorry for that.
> In sync with Thunderbird 2.0.0.24, the SeaMonkey team is preparing for the last security and stability release from the Mozilla 1.8 branch.
>
> The planned shipping date for SeaMonkey 1.1.19 is today, the announcement will be about the end of life for SeaMonkey 1.x, with 1.1.19 being an improvement to 1.1.18 but NOT fixing all known security issues.
>
SeaMonkey 1.1.19 builds in Japanese are available at ..
[LangPack]
http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.langpack.xpi
MD5 = 8938c756eb55096dfb940789546052ae
[Linux]
http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.linux-i686.tar.gz
MD5 = a53a750830ead3cc5df36bc17c5fda70
[Mac]
http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.mac.dmg
MD5 = 36123fdd66f600a34287c07109f14928
[Windows Installer]
http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.win32.installer.exe
MD5 = 9f7d6730ef4210ea804269967a09e024
Upload please.
Thanks!
-----------------------------------
Youhei Tooyama
mozilla...@gmail.com
SeaMonkey-ja L10n Staff
Thanks, uploaded to Mozilla servers.
Robert Kaiser
SeaMonkey 1.1.19 does not work on MacOS X 10.2/10.3/10.4
But , SeaMonkey 1.1.18 does work.
Please Check it!
> Hi Robert Kaiser
> and Everyone !
>
> On 2010/03/15, at 23:29, Robert Kaiser wrote:
>
>> Hi localizers,
>>
>> I just realized I forgot to send a note here, and I'm sorry for that.
>> In sync with Thunderbird 2.0.0.24, the SeaMonkey team is preparing for the last security and stability release from the Mozilla 1.8 branch.
>>
>> The planned shipping date for SeaMonkey 1.1.19 is today, the announcement will be about the end of life for SeaMonkey 1.x, with 1.1.19 being an improvement to 1.1.18 but NOT fixing all known security issues.
>>
> SeaMonkey 1.1.19 builds in Japanese are available at ..
>
> [LangPack]
> http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.langpack.xpi
> MD5 = 8938c756eb55096dfb940789546052ae
> [Linux]
> http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.linux-i686.tar.gz
> MD5 = a53a750830ead3cc5df36bc17c5fda70
> [Mac]
> http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.mac.dmg
> MD5 = 36123fdd66f600a34287c07109f14928
> [Windows Installer]
> http://ftp.seamonkey.jp/seamonkey-1.1.19.ja-JP.win32.installer.exe
> MD5 = 9f7d6730ef4210ea804269967a09e024
>
We have heard some of those reports, but we can't understand what's up
so far. We also are wondering how much time we should dedicate to a
product that is end-of-lined. Still, if we would know a solution, we
could possibly re-build this Mac version, but we have no clue. The build
machine is Tiger and unchanged since 1.1.18, so the problem must be in
the actual code.
Robert Kaiser
Thanks, uploaded to Mozilla servers.
Robert Kaiser
Regards,
Rimas
Thanks, uploaded to Mozilla servers.
Robert kaiser