Closed Bug 738407 Opened 9 years ago Closed 9 years ago

Migrate 3.6 beta users away from that version/channel for EOL

Categories

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

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: akeybl, Assigned: nthomas)

References

Details

Attachments

(1 file, 2 obsolete files)

We should prepare updates to bring forward all 3.6 beta users to FF13 beta with a minor update that has add-on compatibility checks disabled, to be pushed out on or soon after 4/24.
Component: Release Engineering → Release Engineering: Releases
QA Contact: release → bhearsum
I wonder if we can have a custom landing page for these users to provide an explanation of the change. If we loaded a what's new page after the update which appended ?oldversion=3.6.28&channel=beta we'd at least have the option (I'm completely ignoring how feasible using that is on the web side). akeybl, what do you think ? It'd be an change that'd need to land in latest betas to work.
linking per channel mtg.
Depends on: 739793
(In reply to Nick Thomas [:nthomas] from comment #1)
> I wonder if we can have a custom landing page for these users to provide an
> explanation of the change. If we loaded a what's new page after the update
> which appended ?oldversion=3.6.28&channel=beta we'd at least have the option
> (I'm completely ignoring how feasible using that is on the web side).
> akeybl, what do you think ? It'd be an change that'd need to land in latest
> betas to work.

To close the loop on this, we're going with bug 739793 and a custom WN page for updates from 3.6 to FF12.

I'd like to note that we'll need to push 3.6 beta users to the FF12 beta forever since FF13 will no longer support Win2K and XP SP1.
Ok, so 3.6.13 thru 3.6.28 to the latest 12.0 beta, a minor/automatic update, with extension compatibility checks disabled.
(In reply to Nick Thomas [:nthomas] from comment #4)
> Ok, so 3.6.13 thru 3.6.28 to the latest 12.0 beta, a minor/automatic update,
> with extension compatibility checks disabled.

Sounds good. Thanks!
What's left to do here?
We need to generate, test and deploy:

(In reply to Nick Thomas [:nthomas] from comment #4)
> Ok, so 3.6.13 thru 3.6.28 to the latest 12.0 beta, a minor/automatic update,
> with extension compatibility checks disabled.
Assignee: nobody → nrthomas
Priority: -- → P2
Attached file [cvs] patcher config (obsolete) —
* add 12.0b6, drop everything before 3.6.13
* beta and releasetest only
* point at https://www.mozilla.com/%locale%/firefox/12.0/releasenotes/ for the details, confirming this with Alex.
Attached file [cvs] patcher config (obsolete) —
Fix from value, add past-update for 3.6.27 -> 28.
Attachment #616858 - Attachment is obsolete: true
Attached file [cvs] patcher config
fix up path's, and set schema to 1 in 12.0b6 block (old patcher tag doesn't understand it).
Attachment #616862 - Attachment is obsolete: true
Notes, working from a release-mozilla-1.9.2-major_update job:

# cltbld@linux-ix-slave20
mkdir /builds/tmp/nthomas
cd $_

cvs -d :ext:cltbld@cvs.mozilla.org:/cvsroot co -r UPDATE_PACKAGING_R11_1_MU -d build mozilla/tools/patcher
cd build
cvs -d :ext:cltbld@cvs.mozilla.org:/cvsroot co -r UPDATE_PACKAGING_R11_1_MU -d MozBuild mozilla/tools/release/MozBuild
cvs -d :ext:cltbld@cvs.mozilla.org:/cvsroot co -r UPDATE_PACKAGING_R11_1_MU -dBootstrap mozilla/tools/release/Bootstrap/Util.pm
cvs -d :ext:cltbld@cvs.mozilla.org:/cvsroot co -dpatcher-configs mozilla/tools/patcher-configs
curl -sL https://bugzilla.mozilla.org/attachment.cgi?id=616873 > patcher-configs/moz192-branch-patcher2.cfg

export HGROOT=http://hg.mozilla.org/releases/mozilla-release
perl patcher2.pl --build-tools-hg --tools-revision=UPDATE_PACKAGING_R11_1_MU --app=firefox --brand=Firefox --config=patcher-configs/moz192-branch-patcher2.cfg

ln -s 12.0b6 temp/firefox/3.6.28-12.0b6

# fake out the 3.6.28 files
mkdir -p temp/firefox/3.6.28/ftp/
for p in linux-i686 mac win32; do
  for l in `curl -s http://hg.mozilla.org/releases/mozilla-1.9.2/raw-file/FIREFOX_3_6_28_RELEASE/browser/locales/shipped-locales | cut -d' ' -f1`; do
    touch temp/firefox/3.6.28/ftp/firefox-3.6.28.$l.$p.complete.mar
  done
done
perl patcher2.pl --download --app=firefox --brand=Firefox --config=patcher-configs/moz192-branch-patcher2.cfg

perl patcher2.pl --create-patchinfo --app=firefox --brand=Firefox --config=patcher-configs/moz192-branch-patcher2.cfg

cd temp/firefox/3.6.28-12.0b6/
rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2.test/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-3.6.x-12.0b6-beta-test/
rsync -av -e 'ssh -oIdentityFile=~/.ssh/auspush' aus2.beta/ ffxbld@aus3-staging.mozilla.org:/opt/aus2/snippets/staging/Firefox-3.6.x-12.0b6-beta/

Then backupsnip and pushsnip on Firefox-3.6.x-12.0b6-beta-test.
(In reply to Nick Thomas [:nthomas] from comment #7)
> > with extension compatibility checks disabled.

D'oh, missed this bit.

# aus3-staging
cd /opt/aus2/snippets/staging/Firefox-3.6.x-12.0b6-beta-test/Firefox
for d in *; do find $d -type f -exec sed -i -e "s/^extv.*/extv=$d/" {} \; ; done

cd /opt/aus2/snippets/staging/Firefox-3.6.x-12.0b6-beta/Firefox
for d in *; do find $d -type f -exec sed -i -e "s/^extv.*/extv=$d/" {} \; ; done

Then pushsnip again on Firefox-3.6.x-12.0b6-beta-test.
We shipped all of these today.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
No longer depends on: 752716
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.