Tracking bug for build and release of Firefox 3.6 alpha1

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
8 years ago
4 years ago

People

(Reporter: joduinn, Assigned: joduinn)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(7 attachments, 1 obsolete attachment)

Waiting for "go".
Created attachment 390834 [details] [diff] [review]
don't use l10n-changesets

This patch, along with the one from 502876 should allow us to do a non-localized 3.6a1.

The workflow for starting the release will be as follows:
* Land this patch and the one from 502876 (if it hasn't landed)
* Land a release-firefox-mozilla-central patch to include the correct changeset
* reconfig master
* Manually kick off tag
* Manually kick off source, *_build after tag finishes.

I filed bug 506673 about getting the automation to support an l10n-less release without this patch.
Attachment #390834 - Flags: review?(nthomas)
e-mail says you're doing this, joduinn.
Assignee: nobody → joduinn
Priority: -- → P3
Attachment #390834 - Flags: review?(nthomas) → review+
Created attachment 391419 [details] [diff] [review]
all config changes, except for changeset info
Attachment #391419 - Flags: review?(bhearsum)
Created attachment 391447 [details] [diff] [review]
all config changes, except for changeset info

This patch refreshed to :

- fix error in setting for l10nRevisionFile 
- bring staging-master copy of release-firefox-mozilla-central.py in sync.
Attachment #391419 - Attachment is obsolete: true
Attachment #391447 - Flags: review?(bhearsum)
Attachment #391419 - Flags: review?(bhearsum)
Attachment #391447 - Flags: review?(bhearsum) → review+
Comment on attachment 391447 [details] [diff] [review]
all config changes, except for changeset info

Looks good to me.
Depends on: 507950
Created attachment 392198 [details] [diff] [review]
mozconfig changes

The main purpose of this is to change the update channel to beta, and to use the unofficial branding (depends on bug 507950 to switch the strings from Shiretoko to Namoroka). Along the way it has to remove some symlinks so that we can have separate release mozconfigs for m-c and m-1.9.1. 

The changes here are:
* mozilla2/linux/mozilla-1.9.1 symlink to mozilla-central is removed, replaced with a dir that symlinks the subdirs instead, except for release/
* mozilla2/mac/mozilla-1.9.1/release symlink is removed and replaced with a dir containing mozconfig file
* 1.9.1 configs aren't changing at all, hg copy was used to preserve history
* the mozilla-central mozconfigs get on the beta update channel and point to the unofficial branding for 3.6a1
* the same for staging, except that it never got updated from beta to release originally, so this syncs everything back up

I've done a fair bit of checking here, eg copying a clean and dirty repo using rsync -aL, then diffing the result.


Note that Bug 504953 changed the branding stuff, if you run into bustage there.
Attachment #392198 - Flags: review?(bhearsum)
Comment on attachment 392198 [details] [diff] [review]
mozconfig changes

Looks good!
Attachment #392198 - Flags: review?(bhearsum) → review+
Comment on attachment 392198 [details] [diff] [review]
mozconfig changes

http://hg.mozilla.org/build/buildbot-configs/rev/7dff36d5ea76
Attachment #392198 - Flags: checked-in+
Created attachment 392996 [details] [diff] [review]
all config changes, now with changeset info

same as previous patch, but now with changeset
Attachment #392996 - Flags: review?(bhearsum)
Comment on attachment 392996 [details] [diff] [review]
all config changes, now with changeset info

Looks good to me - in the future, you don't need to update the staging one (but you can if you want).
Attachment #392996 - Flags: review?(bhearsum) → review+
Comment on attachment 392996 [details] [diff] [review]
all config changes, now with changeset info

changeset:   1402:000586c92834
Attachment #390834 - Flags: checked-in+
Attachment #392996 - Flags: checked-in+
Comment on attachment 390834 [details] [diff] [review]
don't use l10n-changesets

changeset:   1401:2b03f1a2b973
Created attachment 393252 [details] [diff] [review]
version bumps
Attachment #393252 - Flags: review?(bhearsum)
Attachment #393252 - Flags: review?(bhearsum) → review-
Comment on attachment 393252 [details] [diff] [review]
version bumps

Beltzner wants us to bump straight to 3.6b1pre/1.9.2b1pre. You also need to update the Nagios monitoring files in mozilla/tools/tinderbox-configs/monitoring - you'll need to get all of the mozilla-central, places, tracemonkey, and electrolysis ones.
Created attachment 393254 [details] [diff] [review]
nagios monitoring bumps

(posted as separate patch, because this is cvs.)
Attachment #393254 - Flags: review?(bhearsum)
Comment on attachment 393252 [details] [diff] [review]
version bumps

mr. b seems fine with this option, so I'm reversing my decision.
Attachment #393252 - Flags: review- → review+
Comment on attachment 393254 [details] [diff] [review]
nagios monitoring bumps

Places, TraceMonkey, and Electrolysis all track mozilla-central, so we need to bump their versions here too.
Attachment #393254 - Flags: review?(bhearsum) → review-
Attachment #393252 - Flags: checked-in+
Comment on attachment 393252 [details] [diff] [review]
version bumps

changeset:   31230:2549c010fc02
Created attachment 393258 [details] [diff] [review]
nagios monitoring bumps (now also with project branches)
Attachment #393258 - Flags: review?(bhearsum)
Comment on attachment 393258 [details] [diff] [review]
nagios monitoring bumps (now also with project branches)

Checking in Firefox_electrolysis.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_electrolysis.txt,v  <--  Firefox_electrolysis.txt
new revision: 1.2; previous revision: 1.1
done
Checking in Firefox_mozilla-central.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_mozilla-central.txt,v  <--  Firefox_mozilla-central.txt
new revision: 1.13; previous revision: 1.12
done
Checking in Firefox_places.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_places.txt,v  <--  Firefox_places.txt
new revision: 1.2; previous revision: 1.1
done
Checking in Firefox_tracemonkey.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_tracemonkey.txt,v  <--  Firefox_tracemonkey.txt
new revision: 1.5; previous revision: 1.4
done
Checking in XULRunner_mozilla-central.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/XULRunner_mozilla-central.txt,v  <--  XULRunner_mozilla-central.txt
new revision: 1.2; previous revision: 1.1
done


The project branches are going to fail their checks until they sync up with mozilla-central, but that's OK.
Attachment #393258 - Flags: review?(bhearsum)
Attachment #393258 - Flags: review+
Attachment #393258 - Flags: checked-in+
Comment on attachment 390834 [details] [diff] [review]
don't use l10n-changesets

Backed this out in changeset:   1411:7023dfc6bbf7
 now that we've shipped.
Attachment #390834 - Flags: checked-in+ → checked-in-
shipped friday, so closing.
Status: NEW → RESOLVED
Last Resolved: 8 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.