SeaMonkey 2.1rc2 Release Notes
NoOp
release notes appear to be the same as 2.1rc1. What changes were made
between rc1 & rc2?
Justin Wood (Callek)
> http://www.seamonkey-project.org/releases/2.1rc2
> release notes appear to be the same as 2.1rc1.
That is because those release notes are actually designed for 2.1 final.
What changes were made
> between rc1& rc2?
>
* The bug where Themes would be marked incompatible on first launch is
now fixed. (This is what caused the rc2)
Also Fixed as Ridealongs:
* Bug 657215 - Default search engine does not show as selected in
Preferences
* Bug 656886 - Context menu broken in non-browser sidebars
* New Locales for 2.1: en-GB, tr.
Known Issues in 2.1rc2 -- only (We'll spin a 2.1 final, separately which
fixes this)
* Debug & QA extension is shipped by accident.
* SeaMonkey effective version is set as 2.1pre
Both those issues were due to a mistake in releng. (Same underlying
mistake) luckily easy to fix, and we can move forward with everything
with only minimal "internal" testing.
--
~Justin Wood (Callek)
NoOp
Thanks Justin.
Gary
Justin Wood (Callek)
> On 06/06/2011 04:59 PM, Justin Wood (Callek) wrote:
>> On 6/6/2011 7:21 PM, NoOp wrote:
>>> http://www.seamonkey-project.org/releases/2.1rc2
>>> release notes appear to be the same as 2.1rc1.
>>
>> That is because those release notes are actually designed for 2.1 final.
>>
>> What changes were made
>>> between rc1& rc2?
>>>
>>
>> * The bug where Themes would be marked incompatible on first launch is
>> now fixed. (This is what caused the rc2)
>>
>> Also Fixed as Ridealongs:
>> * Bug 657215 - Default search engine does not show as selected in
>> Preferences
>> * Bug 656886 - Context menu broken in non-browser sidebars
>> * New Locales for 2.1: en-GB, tr.
>>
>> Known Issues in 2.1rc2 -- only (We'll spin a 2.1 final, separately which
>> fixes this)
>> * SeaMonkey effective version is set as 2.1pre
>>
>> Both those issues were due to a mistake in releng. (Same underlying
>> mistake) luckily easy to fix, and we can move forward with everything
>> with only minimal "internal" testing.
>>
>
> Thanks Justin.
You're welcome, though I forgot one issue that is fixed.
In 2.1rc2 Build 1 we noticed that optional extensions were not packaged
in l10n-repacks of the windows installer. (And likely not in the l10n
updates of windows installer, but didn't bother to check that give the
first issue).
We had a large delay in building build2 due to this issue, and with huge
thanks to nthomas for helping to diagnose, and KaiRo for feedback and
help on the procedural issues we got that fixed for what is now our rc2.
So I'm not certain if that existed in 2.1rc1, (we didn't notice at
first, but it surely could have [probably did]). But either way, it is
fixed.
--
~Justin Wood (Callek)
MCBastos
world:
> * The bug where Themes would be marked incompatible on first launch is
> now fixed. (This is what caused the rc2)
Yeah, this is working now. MUCH better. Doesn't feel buggy at all.
However...
Javascript Debugger is still marked as "incompatible with 2.1pre". I
even tried uninstalling it, and then reinstalling 2.1rc2 over itself (in
custom mode) to reinstall it, to make sure I was getting the "right"
version. No dice: still marked as "incompatible." This wouldn't keep me
from using 2.1 (I don't do Javascript programming, therefore the
debugger is not an essential tool for me), but it's still annoying.
I wonder if it has anything to do with the version being set as "2.1pre"?
Some third-party extensions are tagged as "incompatible" too, but that's
to be expected, I guess -- some of them, like Enigmail, might just be
waiting for the official final release. Others, unfortunately, seem to
have been abandoned by their authors. Well, I guess it's wait and see
which of them will be updated...
--
MCBastos
This message has been protected with the 2ROT13 algorithm. Unauthorized
use will be prosecuted under the DMCA.
-=-=-
... Sent from my Casio DataMemo.
*Added by TagZilla 0.066.2 running on Seamonkey 2.0.14 *
Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla
Tony Mechelynck
> Interviewed by CNN on 06/06/2011 20:59, Justin Wood (Callek) told the
> world:
>
>
>> * The bug where Themes would be marked incompatible on first launch is
>> now fixed. (This is what caused the rc2)
>
> Yeah, this is working now. MUCH better. Doesn't feel buggy at all.
> However...
>
> Javascript Debugger is still marked as "incompatible with 2.1pre". I
> even tried uninstalling it, and then reinstalling 2.1rc2 over itself (in
> custom mode) to reinstall it, to make sure I was getting the "right"
> version. No dice: still marked as "incompatible." This wouldn't keep me
> from using 2.1 (I don't do Javascript programming, therefore the
> debugger is not an essential tool for me), but it's still annoying.
>
> I wonder if it has anything to do with the version being set as "2.1pre"?
>
> Some third-party extensions are tagged as "incompatible" too, but that's
> to be expected, I guess -- some of them, like Enigmail, might just be
> waiting for the official final release. Others, unfortunately, seem to
> have been abandoned by their authors. Well, I guess it's wait and see
> which of them will be updated...
>
I think that this might be due to the fix for bug 627240, which packages
the built-in extensions somewhere where they won't be seen by the
extensions manager, except immediately after a SeaMonkey version change,
and even then, only if there is a version increase in the extension itself.
If you can't wait for SeaMonkey 2.1, try the following with the 2.1rc2
you just installed:
1. "Uninstall" JavaScript Debugger, ChatZilla, Debug&QA UI, and DOM
Inspector, and restart SeaMonkey: the "old" versions of these extensions
will now be missing in the addons manager. (This step is not strictly
necessary for ChatZilla, or for any extension whose version number has
changed.) -- If you can't uninstall them (because the Uninstall button
is greyed out) then don't reinstall SeaMonkey over itself, but uninstall
and reinstall it, to clear away any files which have disappeared between
one version and the next. (This leaves your profile untouched.)
2. In about:config, set the preference extensions.lastAppVersion to
2.1b99 then restart SeaMonkey again: it should check your extensions for
compatibility, and after that these four extensions should be back --
but with all the bugfixes which they received in this new version. In
particular, when you launch ChatZilla, you should see 0.9.87 at the top
of its client tab.
Best regards,
Tony.
--
Even if you do learn to speak correct English, whom are you going to
speak it to?
-- Clarence Darrow
Jens Hatlak
> Javascript Debugger is still marked as "incompatible with 2.1pre".
I don't know about 2.1RC2 (which identifies itself incorrectly) but in
general this is covered by the Released Notes, section Known Issues. For
questions about this, Enigmail and more, see the 2.1 FAQ:
<https://wiki.mozilla.org/SeaMonkey/2.1/FAQ>
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>