Releases/SampleBuildNotes: Difference between revisions

Replaced content with "When doing a release you should follow the checklist. = Notes = == Build 1 == === Hit issue X ==="
(Replaced content with "When doing a release you should follow the checklist. = Notes = == Build 1 == === Hit issue X ===")
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Please note that this is NOT a template. You should NOT copy and paste it anywhere. It's only purpose is to provide an example of what build notes could look like when using [[Releases/RelEngChecklist | the checklist]]. Each release is a unique snowflake and will look slightly differently.
When doing a release you should follow [[Releases/RelEngChecklist | the checklist]].
When doing a release you should follow [[Releases/RelEngChecklist | the checklist]].
= Checklist =
* <strike>[[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Starting_a_Release#Setting_reserved_slaves | Set reserved_slaves]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Starting_a_Release#Locking_slaves | Check to make sure you have all of the different types of slaves that you need]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Preparation#Starting_the_automation | Start the automation]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Build#E-mail_Metrics | E-mail Metrics]]</strike>
* <strike>[https://intranet.mozilla.org/RelEngWiki/index.php/Signing#Android_Signing Sign Android builds]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Build#Reset_reserved_slaves | Reset reserved_slaves]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Updates#Publish_Fennec | Publish Fennec]]</strike>
* <strike>[[Release:Release_Automation_on_Mercurial:Updates#Push_snippets | Run pushsnip]]</strike>


= Notes =
= Notes =
== Build 1 ==
== Build 1 ==
=== Started the Release ===
=== Hit issue X ===
* Shipped the l10n milestone
* Set "any master", "mozilla-beta", "any builder" for a clobber
* Set reserved slaves to 8
* Verified that bm13 had enough win32, linux, linux64, and r5 lion machines available to it
* Landed config updates, tagged buildbot-configs, buildbotcustom, and tools with {FIREFOX,FENNEC}_14_0b7_{RELEASE,BUILD1}
* Updated and reconfiged the master
* Ran release sanity dry run:
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u bhearsum -V 14.0b7 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  \
    --dryrun localhost:9001
* No problems, started the automation by running release sanity again without --dryrun
 
=== E-mail Metrics ===
Sent
Firefox,firefox,firefox,14.0b7,14.0
Fennec,firefox-mobile,fennec,14.0b7,14.0
 
=== Signed Android Builds ===
<pre>
cd ~/signing-work/mozharness
hg pull -u && hg up -C
python2.6 ~/signing-work/mozharness/scripts/sign_android.py --config-file signing/android_mozilla-beta.py --platform android
</pre>
 
=== Reset reserved slaves ===
Reset to 0.
 
=== Published Fennec ===
* Bumped version in http://hg.mozilla.org/build/braindump/raw-file/default/releases-related/push_fennec.sh to 14.0b7
* Ran it:
# ffxbld@stage
wget -O push_fennec.sh http://hg.mozilla.org/build/braindump/raw-file/default/releases-related/push_fennec.sh
bash push_fennec.sh
 
* Downloaded multilocale apk (http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/14.0b7/android/multi/fennec-14.0b7.multi.android-arm.apk)
* Browsed to https://market.android.com/publish
* Clicked "Firefox Beta" product
* Clicked "APK Files" tab
* Clicked "Upload APK", uploaded the previously downloaded one.
* Activated the new APK
* Deactivated the previous one
* Clicked "Save"
 
=== Pushed beta snippets ===
cd /opt/aus2/snippets/staging
~/bin/pushsnip Firefox-14.0b99-build1
 
= Bugs Hit =
canmove, Confirmed users
6,439

edits