392551 - Tracking bug for 2nd Thunderbird Major Update (TB1.5.0.14 -> 2.0.0.?)

Status: RESOLVED DUPLICATE of bug 408906

(Release Engineering :: General, defect, P3)

Description

[Carsten Book [:Tomcat]]

Since Thunderbird Major Update is live now, there needs also a Major Update Path from Thunderbird 1.5.0.13 (and following versions of Thunderbird 1.5x) to Thunderbird 2.0.0.6 (or later).

Comment 1

[Scott MacGregor]

One possibility to reduce the world load would be to wait on the next major update offering until we do the last supported 1.5.0.x release.

Comment 2

[Przemyslaw Bialik]

From http://www.mozilla.com/en-US/thunderbird/all.html
> Thunderbird 1.5: This version of Thunderbird will be supported until October 18, > 2007 with security and stability updates. We strongly encourage all users to 
> upgrade to Thunderbird 2.
As 1.5.0.13 (or 1.5.0.14 if released before 18 Oct ?) would be last 1.5.0.x release, when major update could be offered for those users ?

Comment 3

[Daniel Veditz [:dveditz]]

This can't actually block Thunderbird 1.5.0.14 since that release is a prerequisite for doing another Major Update.

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Reopening, because it seems bug#408906 is not a DUP after all - see details in https://bugzilla.mozilla.org/show_bug.cgi?id=408906#c12 and https://bugzilla.mozilla.org/show_bug.cgi?id=408906#c13.

Updating summary to clarify that this bug is tracking the TB major update listed on http://wiki.mozilla.org/Releases (currently scheduled for late-Feb2008). Now that we've shipped the end-of-life release (last week's TB 1.5.0.14), we at least know the release which we will major-update *from*. Obviously, the version we major-update *to* depends on the exact state of the TB2.0.0.x branch, but that will be more clear as we get closer to the ship date.

Comment 6

[J. Paul Reed [:preed]]

(In reply to comment #5)
> Reopening, because it seems bug#408906 is not a DUP after all - see details in
> https://bugzilla.mozilla.org/show_bug.cgi?id=408906#c12 and
> https://bugzilla.mozilla.org/show_bug.cgi?id=408906#c13.

The comments you refer to don't explain why this is NOT a duplicate bug at all.

All the work to do the TB MU is going on in bug 408906, so I don't know why reopening this bug is anything more than playing with Bugzilla semantics, for no apparent benefit to actually completing the work.

Could you please clarify?

> Obviously, the version we major-update *to* depends on the exact state of the
> TB2.0.0.x branch, but that will be more clear as we get closer to the ship
> date.

This statement also makes no sense to me; what do you mean by "depends on the exact state of the TB2.0.0.x branch (which I assume you mean the Mozilla 1.8 branch, since there is no "TB2.0.0.x branch," as such)?

Is there any known reason to NOT update to 2.0.0.9 (beyond the scheduling conflicts you've noted)?

It would probably be good to put your answers, John, in the bug that where the work is going on (bug 408906), and where everyone who's watching this issue is actually discussing it.

Comment 7

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Triaged.

Comment 9

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.