SeaMonkey 2.2 Beta 3 Release -- Introduces New Features
Justin Wood (Callek)
languages and makes a list of new functionality available to a wider
testing audience for the first time. Please note that this pre-release
version is still intended for testers only and might still show some
problems in everyday use. As always, we appreciate any feedback you may
have and encourage users to help us by filing bugs.
This version is built on top of Gecko 5 and features the following new
improvements:
CSS Animations [2] are now supported.
Improved canvas, JavaScript, memory, and networking performance.
Improved standards support for HTML5, XHR, MathML, SMIL, and canvas.
Improved spell checking for some locales.
WebGL content can no longer load cross-domain textures. [3]
Background tabs have setTimeout and setInterval clamped to 1000ms
to improve performance. [4]
Major changes since 2.2b2:
Opening message attachment does not work (Bug 665313)
Added Locales {fi, hu, nb-NO, pt-PT, tr} to bring total
translations up to 20.
The changes page [5] lists a more detailed overview of new features and
fixes relative to our last stable release, SeaMonkey 2.1. [6]
We welcome any and all discussions on this beta on our newsgroups, or
you can even file a bug if you find one. Be sure to check our Known
Issues prior to filing bugs.
SeaMonkey 2.2 Beta 3 is available for free download on the SeaMonkey
website. Once you have downloaded and installed this release, we'd like
to encourage you to get involved in discussing and reporting problems as
well as further improving the product.
Thanks for testing and helping us to make SeaMonkey even better!
Links:
[1] - http://www.seamonkey-project.org/releases/2.2b2
[2] - https://developer.mozilla.org/en/CSS/CSS_animations
[3] -
http://hacks.mozilla.org/2011/06/cross-domain-webgl-textures-disabled-in-firefox-5/
[4] - https://bugzilla.mozilla.org/show_bug.cgi?id=633421
[5] - http://www.seamonkey-project.org/releases/seamonkey2.2/changes
[6] - http://www.seamonkey-project.org/releases/seamonkey2.1/
Further Notes not part of announcement:
(2.2 final is slated for Tuesday, midday, this week we'll have users on
beta of 2.0 test updates to 2.2 and within the next 2 weeks we'll issue
release-updates for 2.0 to 2.2)
There is also the *chance* there will be a 2.2.1 sometime in July to
address issues with Mac 10.7, details will follow if that happens.
WLS
NoOp
> SeaMonkey 2.2 Beta 2 is available for free download [1] now in 14
> languages and makes a list of new functionality available to a wider
> testing audience for the first time. Please note that this pre-release
> version is still intended for testers only and might still show some
> problems in everyday use. As always, we appreciate any feedback you may
> have and encourage users to help us by filing bugs.
I think you mean:
Bill Davidsen
release. Could someone clarify how you can have enough resources to build four
x86_64 Linux versions every night and not just once per release?
No, I don't lack for places to get an onofficial versions, for the same of
reporting bugs I use a nightly of the next version which comes from the official
site, as opposed to getting a build or building from source.
It only takes once being told "we do not support versions build by third parties
for unsupported architectures" (a polite way to say go shit in your hat) to get
me to grab one from an official source.
Besides, they seem to work very well, I'm not unappreciative, just want to be
able to report a bugs I do find.
--
Bill Davidsen <davi...@tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
Justin Wood (Callek)
> NoOp wrote:
>> On 07/03/2011 12:57 AM, Justin Wood (Callek) wrote:
>>> SeaMonkey 2.2 Beta 2 is available for free download [1] now in 14
>>> languages and makes a list of new functionality available to a wider
>>> testing audience for the first time. Please note that this pre-release
>>> version is still intended for testers only and might still show some
>>> problems in everyday use. As always, we appreciate any feedback you may
>>> have and encourage users to help us by filing bugs.
>>
>> I think you mean:
>>
>> http://www.seamonkey-project.org/releases/2.2b3
>> ...
> Robert claimed that lack of build resources was why Linux_x86-64 doesn't
> have a release. Could someone clarify how you can have enough resources
> to build four x86_64 Linux versions every night and not just once per
> release?
>
> No, I don't lack for places to get an onofficial versions, for the same
> of reporting bugs I use a nightly of the next version which comes from
> the official site, as opposed to getting a build or building from source.
>
> It only takes once being told "we do not support versions build by third
> parties for unsupported architectures" (a polite way to say go shit in
> your hat) to get me to grab one from an official source.
>
> Besides, they seem to work very well, I'm not unappreciative, just want
> to be able to report a bugs I do find.
>
We *do* build linux x86_64 on EVERY release, beta and otherwise. We put
those builds in contrib/*.
We don't officially support them because we don't have the resources to
support a variety of things, testing, automated testing, QA, etc.
We provide them just don't officially support. No l10n builds for the
platform either, fwiw.
We tried to even get updates going for release builds of linux64 for 2.2
(we hit a snag, and won't delay 2.2 for a linux64 issue atm), and KaiRo
was even able to manually create updates (to 2.0.14) from all prior 2.0
linux64 builds we produced.
And in reality not sure where you get "4 every night" we only create
every night trunk/aurora linux64 builds, we have "on change" builds of
linux64 that happen whenever the slave itself is free but it is ONLY one
slave, so if the tree changes are heafty it gets pretty behind.
--
~Justin Wood (Callek)
Robert Kaiser
> KaiRo
> was even able to manually create updates (to 2.0.14) from all prior 2.0
> linux64 builds we produced.
Just for clarification, I haven't put them online yet for the normal
channels, but will do so once I get around to it. I can also put up such
manually created full updates for the 2.1/2.2 betas and releases.
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community should think about. And most of the
time, I even appreciate irony and fun! :)
Justin Wood (Callek)
> to be able to report a bugs I do find.
O, since I seemed to have missed this point in your post,
While we do not 'officially' support Linux64, we do have a goal of doing
so at some point in the future, when we do have more build machines, etc.
So feel *free* to report bugs against us from a linux64 build without
direct fear of being wontfixed*
* -- ..because it is a linux64 machine you reported it on, we still
reserve the right to WONTFIX in general.
--
~Justin Wood (Callek)