Closed Bug 720822 Opened 10 years ago Closed 10 years ago

Migrate 3.6 nightly users away from that version/channel before disabling nightlies

Categories

(Release Engineering :: Release Requests, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: akeybl, Assigned: nthomas)

Details

Attachments

(1 file)

This bug is meant to address where to migrate our 3.6 nightly users to before disabling nightlies. I think the next action would be to list our options (moving them to 3.6 beta, moving them to FF10, etc.)
It looks like we aren't going to do this as soon as I'd hoped.
Priority: -- → P3
found in triage.
Component: Release Engineering → Release Engineering: Releases
QA Contact: release → bhearsum
This was touched upon in the 3/20 channel meeting. We'd like to scope pushing these 3.6 users to the ESR nightlies to have some test coverage there without advertising the channel. If it's deemed to be too difficult, let's just push them to the nightly channel.
One additional note: it'd be preferable to disable the add-on compatibility check here.
per channel mtg:

1) When we EOL FF3.6, we want to bring the ~2000 FF3.6 nightly users forward to a supported version of Firefox. akeybl's first preference would be to bring them to latest nightly build on ESR train, to help with ESR nightly coverage. However, if that is more complex/risky, he's fine with instead migrating them to latest mozilla-central nightly. The effort spent on this should be commensurate with the number of users here.

2) these updates are to be flipped "live" on or soon after 4/24 (see related EOL work in bug#738407).
Migrating 3.6 nightly to m-c nightly is a one line config change at
 http://mxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.php#140
because the channel doesn't need to change.

Migrating 3.6 nightly to esr on 'nightly-esr10' is more involved. We'd need to create channel changing mar files (1 for mac & 1 for everything else), and snippets pointing to those files. We'll need to do something similiar for bug 657789 so we'll need to create a process anyway.
(In reply to Nick Thomas [:nthomas] from comment #6)
> Migrating 3.6 nightly to m-c nightly is a one line config change at
>  http://mxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.
> php#140
> because the channel doesn't need to change.
> 
> Migrating 3.6 nightly to esr on 'nightly-esr10' is more involved. We'd need
> to create channel changing mar files (1 for mac & 1 for everything else),
> and snippets pointing to those files. We'll need to do something similiar
> for bug 657789 so we'll need to create a process anyway.

per channel mtg w/akeybl: 

1) lets do whatever is easiest, which aiui from above, is to migrate 3.6 nightly to m-c nightly.

2) can we do this next early week?
I propose we write and land the patch today, but let it sit for deployment until we unthrottle the FF12 updates early next week.
Assignee: nobody → nrthomas
Priority: P3 → P2
This will send the ~500 FF 3.5.x and ~1k FF 3.6.x nightly users to mozilla-central, supposing their OS hasn't been desupported (and they can actually apply an update). 

Thunderbird is going the comm-central for their 1.9.2 branch, but this won't apply until we switch them to aus3.m.o. Standard8 OK that at bug 745526 comment #13.
Attachment #618809 - Flags: review?(bhearsum)
Comment on attachment 618809 [details] [diff] [review]
[cvs] all old Firefox and Thunderbird nightlies go to *-central

Review of attachment 618809 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good to me.
Attachment #618809 - Flags: review?(bhearsum) → review+
Comment on attachment 618809 [details] [diff] [review]
[cvs] all old Firefox and Thunderbird nightlies go to *-central

Checking in inc/config-dist.php;
/cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v  <--  config-dist.php
new revision: 1.206; previous revision: 1.205
done
Attachment #618809 - Flags: checked-in+
This was deployed by bug 749885 on 2012-04-27.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.