Chris Ilias wrote:
I wrote " bugs with 2.1 or 2.2 *or upgrade there-to* ..."
So master Ilias, you claim that problems with upgrading from say
SM 2.0.14 to SM 2.2 will be addressed in a later/future SM release?
Would you care to explain how you expect that to work?
Also do you claim to dispute what I write in " Any person who is on
say SM 2.2 ... its own basket of fresh bugs."
If there's a bug regard to updating from from 2.0.x to 2.2 that doesn't
exist when updating from 2.0.x to 2.3, then I think the bug is no longer
valid, because the update mechanism (I think) will bypass 2.2 after 2.3
is released (i.e. 2.0.x user will be offered 2.3). Justin, is that right?
There are two things at play here.
1) Bugs that exist in 2.2 may (and many are) be fixed in SeaMonkey 2.3
2) Bugs that exist only from upgrading to 2.2 and will not be fixed
magically when you migrate 2.2->2.3
The latter is what I'll address since it was your specific Question.
At present we don't have a codepath setup to upgrade users from 2.0 to
2.3, but we are close. I expect within the next 2 weeks I'll have that
upgrade available. In the mean time, 2.0 will still be upgraded to 2.2
and then to 2.3.
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
