On 6/19/2011 10:18 PM, Rostyslaw Lewyckyj wrote:
Justin Wood (Callek) wrote:
On 6/19/2011 9:37 PM, Jim wrote:
Why doesn't SM 2.0.14 list SM 2.1 as an update?
Because we don't have MU (Major Update) Offers setup yet.
Those require a bit more intensive testing as they follow a slightly
different update path.
Ok.
So when do you expect the release announcement for SM 2.2 ,
after its' 'more intensive' testing process to be ready
via this MU mechanism? :)
Well its a separate update Mechanism that we need to test (and create
specially) separate from the actual release of SeaMonkey 2.2 fwiw.
From what you wrote previously I gather that there is not going to be
a 2.1.xx series of 'fix it up' releases.
There will not be a special 2.1.x series of fix-it-up releases, correct.
The security update to 2.1 will be 2.2, etc.
At this point, it is looking like we will offer _prompted_ MU updates
from 2.0 and 2.1 to 2.2 as soon as we can (we can initially hoped to
offer MU to 2.1 but it seems that if we delay the 2.2 release to do
that, there *may* be a security issue or two and I'd rather have
security fixes in place).
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
