Closed
Bug 507967
Opened 16 years ago
Closed 16 years ago
Stop offering major update to 3.0.12 users
Categories
(Release Engineering :: General, defect, P1)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: samuel.sidler+old, Assigned: nthomas)
References
Details
We should stop offering our major update to users of Firefox 3.0.12 a few hours before releasing 3.0.13 (let's say, midnight tonight or so). The rationale for this is basically that as soon as word hits we're shipping 3.0.13 tomorrow, many users will do a "Check for Updates..." to get that release, but will instead be offered 3.5.1. That's not the best user experience for 3.0.x users.
I asked Nick and he said this wouldn't be too hard to do for this release, but we should make it part of our regular release process as well. I can file a bug for that, if needed.
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → nthomas
Priority: -- → P1
Assignee | ||
Comment 1•16 years ago
|
||
# cltbld@aus2-staging
cd /opt/aus2/snippets/staging/
rsync -a 20090721-Firefox-3.0.12-3.5.1-MU/ 20090802-Firefox-3.0.12-3.5.1-MU-null/
cd 20090802-Firefox-3.0.12-3.5.1-MU-null/
find . -depth -type d -iregex '.*/beta$' -exec rm -rf {} \;
for f in `find . -type f`; do rm $f; touch $f; done
Checked that there 370 empty snippets, to match 370 useful ones in the source dir, release channel only.
~/bin/backupsnip 20090802-Firefox-3.0.12-3.5.1-MU-null
~/bin/pushsnip 20090802-Firefox-3.0.12-3.5.1-MU-null
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•