Releases/Firefox 13.0b7/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 105: Line 105:
All automated; no problems \o/
All automated; no problems \o/


'''DONE TO HERE'''
Reset reserved_slaves to 0


=== Going to Beta ===
=== Going to Beta ===


==== Run backupsnip ====
==== Run backupsnip ====
NOTE: Remember to do this at least '''2 hours''' ahead of the expected "go to beta" email. <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Prepare_for_Beta_Release_.28Firefox_only.29|details]]''</small>
<pre>
 
backupsnip Firefox-13.0b7-build1
Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on.  If you intend to use screen, initiate your screen session while you are still yourself.
</pre>


==== Push to beta ====
==== Push to beta ====
Wait for "go" from release managers<br />
Wait for "go" from release managers<br />
For Firefox:
For Firefox:
* Publish (and record run time here): <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Beta_Release_.28Firefox_only.29|details]]''</small>
* Publish (and record run time here):  
* on completion, email r-d that VERSION updates are live on the beta channel
<pre>
pushsnip Firefox-13.0b7-build1
 
cat Firefox-13.0b7-build1.time
real 285.03
user 1.70
sys 5.44
</pre>


Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.
Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.

Latest revision as of 18:36, 1 June 2012

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

Build Engineers

{catlee} - Tracking bug: bug 760219

Signed-off Revision(s)

Build 1: b8b0ed817c31

L10N changesets

Instructions on how to get them

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
1 GECKO130_2012053115_RELBRANCH, FIREFOX_13_0b7_BUILD1 FIREFOX_13_0b7_RELEASE b8b0ed817c31

Build data

Firefox

Build # Type Build ID Build machine Time to build
1 Linux 20120531155942 linux-ix-slave14 1 hrs, 7 mins, 8 secs
Linux64 linux64-ix-slave21 1 hrs, 5 mins, 50 secs
Mac moz2-darwin10-slave42 3 hrs, 21 mins, 10 secs
Windows mw32-ix-slave13 3 hrs, 30 mins, 34 secs


Notes

Build 1

Preparing to start Automation

  • Set clobbers for release-mozilla-beta on all masters
  • Set reserved slaves on bm13:
[cltbld@buildbot-master13 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master13 master]$ cat reserved_slaves
5
  • Create candidates link:
# ffxbld@stage
cd /pub/mozilla.org/firefox/nightly/
mkdir ../candidates/13.0b7-candidates
ln -s ../candidates/13.0b7-candidates 13.0b7-candidates
  • Tag buildbot-configs, buildbotcustom, & tools with build & release tags. (details)
hg tag -f FIREFOX_13_0b7_RELEASE FIREFOX_13_0b7_BUILD1
  • update and reconfigure the master
cd /builds/buildbot/build1/master
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u catlee -V 13.0b7 --branch mozilla-beta --build-number 1 \
    --release-config release-firefox-mozilla-beta.py --products firefox --dryrun localhost:9001
  • start automation
    • the same command as above but without the "--dryrun"

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org". Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on #metrics. 

Firefox,firefox,firefox,13.0b7,13.0

Tag -> Ready for release

All automated; no problems \o/

Reset reserved_slaves to 0

Going to Beta

Run backupsnip

backupsnip Firefox-13.0b7-build1

Push to beta

Wait for "go" from release managers
For Firefox:

  • Publish (and record run time here):
pushsnip Firefox-13.0b7-build1

cat Firefox-13.0b7-build1.time
real 285.03
user 1.70
sys 5.44

Wait for confirmation from QA that each of the above releases is okay, then close the tracking ticket.

Release Day

Push XULRunner to Mirrors

Update XULRunner wiki page

For major releases or chemspills, update the links on:

Also for older releases:

Check Throttling

See http://update-watch.localgho.st/release/ for example AUS links

Some links to check:

Push to Release Channel (for beta releases and release releases)

Once there is enough uptake and we get "go" from release driver.

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_13.0b7/BuildNotes&oldid=436718"