Closed Bug 676083 Opened 15 years ago Closed 15 years ago

tracking bug for build and release Firefox 6.0

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rail)

References

Details

Attachments

(8 files, 2 obsolete files)

Scheduled to be released on August 16th.
Attached patch update staging configs (obsolete) — — Splinter Review
* removed staging_release-firefox-mozilla-release.py, we don't use it anymore * update staging_release-firefox-mozilla-central.py to 6.0
Attachment #551400 - Flags: review?(bhearsum)
In 5.0.1 release we generated beta snippets manually. Wouldn't be safer and easier to enable releaseConfig['useBetaChannel'] (next patch) and apply this patch?
Attachment #551421 - Flags: review?(bhearsum)
Attached patch 6.0 configs (obsolete) — — Splinter Review
* set releaseConfig['oldVersion'] to 1 * bump version
Attachment #551426 - Flags: feedback?(bhearsum)
* fixed oldAppVersion * removed obsoleted mozilla/diffs.sh * fixed file permissions for release-fennec-mozilla-{beta,release}.py * removed obsoleted staging_release-firefox-mozilla-central.py * bump version
Attachment #551400 - Attachment is obsolete: true
Attachment #551400 - Flags: review?(bhearsum)
Attachment #551427 - Flags: review?(bhearsum)
Comment on attachment 551421 [details] [diff] [review] Add beta channel for mozilla-release branch Review of attachment 551421 [details] [diff] [review]: ----------------------------------------------------------------- Yeah, this makes sense. I'm pretty sure I didn't think to do this during 5.0 final.
Attachment #551421 - Flags: review?(bhearsum) → review+
Attachment #551427 - Flags: review?(bhearsum) → review+
Comment on attachment 551426 [details] [diff] [review] 6.0 configs Review of attachment 551426 [details] [diff] [review]: ----------------------------------------------------------------- You're making this look so easy ;). All of the stuff you've got here looks good to me, let's see how the staging run goes!
Attachment #551426 - Flags: feedback?(bhearsum) → feedback+
lunux{,64}: * use gcc-4.5 * enable PGO compare configs: $ for p in linux linux64 win32 macosx64 linux-android linux-maemo5-gtk linux-mobile macosx-mobile win32-mobile; do diff -r $p/mozilla-{beta,release}/release; done| grep -P '^(>|<)' |sort -u < ac_add_options --enable-update-channel=beta > ac_add_options --enable-update-channel=release < ac_add_options --with-branding=mobile/branding/beta > ac_add_options --with-branding=mobile/branding/official < ac_add_options --with-l10n-base=.. > ac_add_options --with-l10n-base=.. Last 2 lines could be ignored, win32/mozilla-{beta,release}/release/l10n-mozconfig have that line, but on different lines.
Attachment #551586 - Flags: review?(nrthomas)
Comment on attachment 551421 [details] [diff] [review] Add beta channel for mozilla-release branch >Index: mozRelease-branch-patcher2.cfg >+ past-update 4.0rc1 4.0rc2 betatest releasetest release beta >+ past-update 4.0rc2 4.0.1 betatest releasetest release beta >+ past-update 4.0.1 5.0 betatest releasetest release beta NB: This won't generate updates for 5.0b* and 6.0b* to 6.0 final. We kinda need to generate updates from both configs * mozBeta-branch-patcher2.cfg, to get beta users on to the 6.0 final build, partial from 6.0b5 * mozRelease-branch-patcher2.cfg, to get partials from 5.0/5.0.1 (see 3.6.20 for hints dealing with the split version)
Attachment #551586 - Flags: review?(nrthomas) → review+
Attached patch debsign configs — — Splinter Review
* Bump version * add tag to be consistent with tested beta configs
Attachment #551718 - Flags: review?(aki)
Attachment #551718 - Flags: review?(aki) → review+
What do you think about adding a generic "FENNEC_RELEASE" and "FENNEC_BETA" tag? downsides: * yet another tag upsides: * config files can point to FENNEC_RELEASE instead of FENNEC_6_0_RELEASE and never have to change
Attachment #551586 - Flags: checked-in+
Comment on attachment 551421 [details] [diff] [review] Add beta channel for mozilla-release branch cvs commit -m "Bug 676083 - tracking bug for build and release Firefox 6.0. p=rail, r=bhearsum" cvs commit: Examining . Checking in mozRelease-branch-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/mozRelease-branch-patcher2.cfg,v <-- mozRelease-branch-patcher2.cfg new revision: 1.5; previous revision: 1.4 done
Attachment #551421 - Flags: checked-in+
Attached patch 6.0 configs — — Splinter Review
There is no new l10n changesets available, so I copied beta l10n changesets files to the corresponding release files. TBD to be replaces with the final "go" revision.
Attachment #551426 - Attachment is obsolete: true
Attachment #552521 - Flags: review?
Attachment #552521 - Flags: review?(nrthomas)
Attachment #552521 - Flags: review?(aki)
Attachment #552521 - Flags: review?
Comment on attachment 552521 [details] [diff] [review] 6.0 configs One thing to note -- push_fennec.sh (when pushing live) will also need to update the |latest| softlink, since this is a non-beta. (These softlinks will all go away once maemo is EOLed)
Attachment #552521 - Flags: review?(aki) → review+
Comment on attachment 552521 [details] [diff] [review] 6.0 configs '339923bc045a' for the TBD's.
Attachment #552521 - Flags: review?(nrthomas) → review+
Attachment #552618 - Flags: review?(nrthomas)
Comment on attachment 552618 [details] [diff] [review] mozilla-1.9.2 MU configs >diff --git a/mozilla/release-firefox-mozilla-1.9.2.py b/mozilla/release-firefox-mozilla-1.9.2.py >+releaseConfig['majorUpdateReleaseNotesUrl'] = 'https://www.mozilla.com/%locale%/firefox/6.0/details/' We'll need to use http://www.mozilla.com/%LOCALE%/firefox/latest/details/from-3.6.html here, from bug 668108. Those pages are not up yet.
Attachment #552618 - Flags: review?(nrthomas) → review+
Depends on: 668108
Attachment #552661 - Flags: review?(bhearsum)
Attachment #552661 - Flags: review?(bhearsum) → review+
Attachment #552661 - Flags: checked-in+
Depends on: 679173
Depends on: 679394
Per https://bugzilla.mozilla.org/show_bug.cgi?id=675730#c7 moving dependency on bug 668108 there and closing this one. All done here!
Status: NEW → RESOLVED
Closed: 15 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.

Attachment

General

Created:
Updated:
Size: