Releases/Firefox 34.0/BuildNotes: Difference between revisions
< Releases
Jump to navigation
Jump to search
(→Running tests: moaaar deets) |
(→Checklist: beta update part done) |
||
Line 5: | Line 5: | ||
* <s>(RelMan) [[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]] | * <s>(RelMan) [[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]] | ||
* (RelMan) [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Submit_to_Ship_It | Submit to Ship It]]</s> | * (RelMan) [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Submit_to_Ship_It | Submit to Ship It]]</s> | ||
* [[Releases/Firefox_34.0/BuildNotes#Updates_for_beta | Updates for beta]] | * [[Releases/Firefox_34.0/BuildNotes#Updates_for_beta | Updates for beta]] - prep done, waiting to be able to test | ||
* [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]] | * [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]] | ||
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Do_I_need_to_throttle.3F | Apply Throttling ]] | * [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Do_I_need_to_throttle.3F | Apply Throttling ]] |
Revision as of 10:35, 25 November 2014
Firefox 34.0 build1
Checklist
(RelMan) Ship the l10n milestone(RelMan) Submit to Ship It- Updates for beta - prep done, waiting to be able to test
- Push to mirrors
- Apply Throttling
- Verify throttling
- Run pushsnip
- Post-release tasks
Issues
Updates for beta
cf 33.0 notes
- partial from 34.0b11 generated at build time (from this patch)
- need to check Firefox-34.0-build1 in aus4-admin to make ftpFilenames has entry for 34.0b11 present
Update verify
Prep
On nthomas' laptop, after en-US builds done:
cd <parent_of_tools_checkout, updated to tip> export PERL5LIB="tools/lib/perl:$HOME/perl5/lib/perl5" # need Config::General v2.44 wget http://hg.mozilla.org/releases/mozilla-release/raw-file/FIREFOX_34_0_RELEASE/browser/locales/shipped-locales perl tools/release/patcher-config-bump.pl -p firefox -r Firefox -v 34.0 -a 34.0 -o 34.0b11 -b 1 \ -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg -t stage.mozilla.org -f ftp.mozilla.org \ -d download.mozilla.org -l shipped-locales --partial-version 34.0b11 --platform linux --platform linux64 \ --platform macosx64 --platform win32 # generate update verify configs python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform linux64 --output tools/release/updates/mozBeta-firefox-linux64.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform linux --output tools/release/updates/mozBeta-firefox-linux.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform macosx64 --output tools/release/updates/mozBeta-firefox-mac64.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform win32 --output tools/release/updates/mozBeta-firefox-win32.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE hg -R tools/ diff tools/release/updates > patch
Attached to bug 1071606 as attachment 8528267.
Running tests
Rather than grabbing 3 slaves and running these manually, we may be able to twist the automation's arm:
- wait until we get the 'updates available on betatest' email
- commit the config patch to tools (no fallout from this on next release)
- force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the script_repo_revision property to the revision when that landed
The emails we get back will be labelled 34.0b11, but I don't think it's worth bumping the release config and reconfiging just to avoid that.
Fennec 34.0 build1
Checklist
(RelMan) Ship the l10n milestone(RelMan) Submit to Ship It- Push to mirrors
- Post-release tasks
Issues
- android repacks all failed in configure with java < 1.7, we missed bug 1082325. Patch landed, updated tags and re-triggered jobs, all green.
- email '[release] Fennec 34.0 build1: Updates available on None' with content 'Updates to Fennec 34.0 build1 are now ready for testing on the None channel.' Commented on bug 1019724.