Closed Bug 668741 (SM2.2MU) Opened 13 years ago Closed 13 years ago

Tracking bug for build and release of SeaMonkey 2.2 MU [Major Update]

Categories

(SeaMonkey :: Release Engineering, defect, P1)

SeaMonkey 2.2 Branch
defect

Tracking

(seamonkey2.2+ fixed)

RESOLVED FIXED
seamonkey2.4
Tracking Status
seamonkey2.2 + fixed

People

(Reporter: Callek, Unassigned)

References

()

Details

+++ This bug was initially created as a clone of Bug #668731 +++

+++ This bug was initially created as a clone of Bug #668730 +++

+++ This bug was initially created as a clone of Bug #666867 +++

+++ This bug was initially created as a clone of Bug #647928 +++

For SeaMonkey 2.2 we'll want Major Updates to come from 1.9.1 (SeaMonkey 2.0)

This bug is intended to track that.
Depends on: 668744
Firefox is preparing 3.6.19 and 5.0.1 chemspill releases due to Mac-specific issues. Assuming that this may imply a SM 2.2.1 respin as well, should the MU be delayed for 2.0.x -> 2.2.1 instead?
(In reply to comment #1)
> Firefox is preparing 3.6.19 and 5.0.1 chemspill releases due to Mac-specific
> issues. Assuming that this may imply a SM 2.2.1 respin as well, should the
> MU be delayed for 2.0.x -> 2.2.1 instead?

The chemspill is only for a Mac OS X 10.7 issue, and I don't think enough SeaMonkey users will upgrade that fast to need this - but ultimately, it's Callek's call.
(In reply to comment #2)
> (In reply to comment #1)
> > Firefox is preparing 3.6.19 and 5.0.1 chemspill releases due to Mac-specific
> > issues. Assuming that this may imply a SM 2.2.1 respin as well, should the
> > MU be delayed for 2.0.x -> 2.2.1 instead?
> 
> The chemspill is only for a Mac OS X 10.7 issue, and I don't think enough
> SeaMonkey users will upgrade that fast to need this - but ultimately, it's
> Callek's call.

I was already thinking about this, and long story short -- unless new data flows in to cause me to change my mind, we will not be spinning a 2.2.1. I'll send details to the members list/newsgroups this week.
Data: Lion is scheduled to be released in July and IIUC the "upgrade" costs $29.99.

How fast will SM users upgrade to 10.7? No idea, but you can upgrade through Appstore (which is reachable from a menuitem in the OS).
BTW, do we take into account that 2.0 runs on 10.4, but 2.2 doesn't?
(In reply to comment #5)
> BTW, do we take into account that 2.0 runs on 10.4, but 2.2 doesn't?

Yes, we should not offer updates there. If someone has a 10.4 system around to test, I'd be happy to see if that works, though.
(In reply to comment #6)
> (In reply to comment #5)
> > BTW, do we take into account that 2.0 runs on 10.4, but 2.2 doesn't?
> 
> Yes, we should not offer updates there. If someone has a 10.4 system around
> to test, I'd be happy to see if that works, though.

I'll be happy to test - I have access to an iMac with 10.4.
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > BTW, do we take into account that 2.0 runs on 10.4, but 2.2 doesn't?
> > 
> > Yes, we should not offer updates there. If someone has a 10.4 system around
> > to test, I'd be happy to see if that works, though.
> 
> I'll be happy to test - I have access to an iMac with 10.4.

Karsten tested for me on betatest channel the first time through here. If you want to test on the beta update channel that would be great!

(easiest way to do that, download 2.0b3 (new profile) let it update, THEN let it update again (simply help->check for updates)
(In reply to comment #8)
> Karsten tested for me on betatest channel the first time through here. If
> you want to test on the beta update channel that would be great!
> 
> (easiest way to do that, download 2.0b3 (new profile) let it update, THEN
> let it update again (simply help->check for updates)

Works fine. I downloaded 2.0b2 (yes, no b3), then did "help --> check for updates" and got 2.0.14 (I checked the update channel in about:config and I was on "beta"). Then I did another check for updates and the result was "No updates found".
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.4
You need to log in before you can comment on or make changes to this bug.