Closed Bug 598021 Opened 10 years ago Closed 10 years ago

Publish a major update specifically targeted at TB 3.0.4 users

Categories

(Mozilla Messaging :: Release Engineering, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: jhopkins)

Details

Attachments

(1 file)

We have over 100k users on 3.0.4 - they could be "stuck" there or purposely disabled updates, but the stats imply that it is users on the release channel and spread all over the world. Additionally, we normally end up with something more like 10-30k users on a particular version after a period of time.

So I've got no idea about what it is with 3.0.4, but I'd like to try targeting a major update at those users and see what happens.

So here's what I'd like to see, but only if it is possible

- Publish 3.0.4 -> 3.1.4 Major Updates.
- Also have being offered:
-- 3.0.x -> 3.0.4 (where x < 4)
-- 3.0.x -> 3.0.8 (where x > 5 && x < 8)
-- 3.0.8 -> 3.1.4

If that isn't easily possible, then please let me know what it would take if the update system does allow it.

The alternative is to try and push via start pages - which might be the easier option here.
Note: If you do think this is doable, please publish everything on betatest and get Ludovic and myself to sign-off before releasing.
Looks simple to me, what this ends up being is simply a 3.0.4 => 3.1.4 major update. Exactly the same thing as any other major update.

The only issue here is if we make a 3.0.9 release, when that comes, the update offers for it will be offered to 3.0.4 users, overwriting the 3.1.4 major update.
(In reply to comment #2)
> Looks simple to me, what this ends up being is simply a 3.0.4 => 3.1.4 major
> update. Exactly the same thing as any other major update.

Excellent, make it so! (well, just on betatest/releasetest first).

> The only issue here is if we make a 3.0.9 release, when that comes, the update
> offers for it will be offered to 3.0.4 users, overwriting the 3.1.4 major
> update.

Worst case, we'll re-generate, but hopefully we'll have got the majority of those users off there by then.
This patch does not need to be checked in.  It was used to generate the upgrade snippets for this bug only.
Assignee: nobody → john.hopkins
Status: NEW → ASSIGNED
Upgrade snippets pushed to test channels.
For simplicity we've opted to check in the patch instead.

Checking in moz192-thunderbird-branch-major-update-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz192-thunderbird-branch-major-update-patcher2.cfg,v  <--  moz192-thunderbird-branch-major-update-patcher2.cfg
new revision: 1.10; previous revision: 1.9
done
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.