Releases/BuildNotesTemplate: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 14: Line 14:


=L10N changesets=
=L10N changesets=
[https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#L10N_Changesets Instructions] on how to get them
[https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Configuration#L10N_Changesets Instructions] on how to get them
* Firefox: link to the l10n-changesets
* Firefox: link to the l10n-changesets
* Fennec: link to the json
* Fennec: link to the json


=Tags=
=Tags=
[[Release:Release_Automation_on_Mercurial:Configuration#Starting_the_automation|Manually tag]] the automation code, then record the generated tags below. <small>''([[Release:Release_Automation_on_Mercurial:Documentation#Tag|details]])''</small>
[[Release:Release_Automation_on_Mercurial:Configuration#Starting_the_automation|Manually tag]] the automation code, then record the generated tags below. <small>''([[Release:Release_Automation_on_Mercurial:Build#Tag|details]])''</small>


{| class="fullwidth-table"
{| class="fullwidth-table"
Line 99: Line 99:


===Preparing to start Automation===
===Preparing to start Automation===
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
<small>[[Release:Release_Automation_on_Mercurial:Configuration#Starting_the_automation|detailed instructions]]</small>
* Go and make sure that there are L10n milestones for your release. Otherwise create them
* Go and make sure that there are L10n milestones for your release. Otherwise create them
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
* Set clobbers for the appropriate masters. Doing this 24-48 hours in advance should speedup the build.
Line 109: Line 109:
  ln -s ../candidates/$version-candidates $version-candidates
  ln -s ../candidates/$version-candidates $version-candidates
* Update l10n changesets for desktop, mobile
* Update l10n changesets for desktop, mobile
** [https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#L10N_Changesets Instructions] on how to get them
** [https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Configuration#L10N_Changesets Instructions] on how to get them
** [https://l10n-stage-sj.mozilla.org/shipping/milestones dashboard]
** [https://l10n-stage-sj.mozilla.org/shipping/milestones dashboard]
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Land automation configs (are you or buildduty going to reconfig? great, merge. otherwise double-land only your configs)
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. <small>''([[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|details]])''</small>
* Tag buildbot-configs, buildbotcustom, & tools with build & release tags. <small>''([[Release:Release_Automation_on_Mercurial:Configuration#Starting_the_automation|details]])''</small>
** Sample command for Firefox 10.0 beta 5 build 1:
** Sample command for Firefox 10.0 beta 5 build 1:
<pre>
<pre>
Line 193: Line 193:


=== Unittests / Talos ===
=== Unittests / Talos ===
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Talos_.26_Unittests|details]]</small>
<small>[[Release:Release_Automation_on_Mercurial:Build#Talos_.26_Unittests|details]]</small>
# Look to see that they ran  
# Look to see that they ran  
# Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
# Document any oranges (per platform) for unittests - if possible, try to confirm it's known/random
Line 227: Line 227:
For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.
For instance, the 3.6.26 builds got created a week before the 10.0 release but the "final" 10.0 builds were not created after few days.


Follow instructions from the [[Release:Release_Automation_on_Mercurial:Documentation#Major_Update_.28Firefox_only.29|Major update]] documentation.
Follow instructions from the [[Release:Release_Automation_on_Mercurial:Updates#Major_Update_.28Firefox_only.29|Major update]] documentation.


==== Major Update verify ====
==== Major Update verify ====
Line 236: Line 236:
=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
It is supposed to be triggered automatically after updates are done.
It is supposed to be triggered automatically after updates are done.
File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small>
File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Updates#Antivirus_check|details]]</small>


=== Push to internal mirrors ===
=== Push to internal mirrors ===
Line 254: Line 254:


==== 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>
NOTE: Remember to do this at least '''2 hours''' ahead of the expected "go to beta" email. <small>''[[Release:Release_Automation_on_Mercurial:Updates#Prepare_for_Beta_Release_.28Firefox_only.29|details]]''</small>


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.
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.
Line 261: Line 261:
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): <small>''[[Release:Release_Automation_on_Mercurial:Updates#Beta_Release_.28Firefox_only.29|details]]''</small>
* on completion, email r-d that VERSION updates are live on the beta channel
* on completion, email r-d that VERSION updates are live on the beta channel


Confirmed users
1,018

edits

Navigation menu