ReleaseEngineering:ProjectBranchPlanning: Difference between revisions

ReleaseEngineering:ProjectBranchPlanning (view source)

Revision as of 23:54, 11 May 2011

377 bytes removed , 11 May 2011

→‎Release Engineering Checklist

Lsblakk

Confirmed users

4,467

edits

@@ Line 31: / Line 31: @@
 ** Approx expected life span of project branch?
-= Release Engineering Checklist =
+= Release Engineering Project Branch Creation Checklist =
 * File a ServerOps bug to create repo in hg.m.o if repo does not already exist. Repos should be created under "/projects", "/services" or "/releases" whenever possible.
@@ Line 38: / Line 38: @@
 * Once that is reviewed and landed you can [https://intranet.mozilla.org/RelEngWiki/index.php/How_To/Update_Tinderbox_Pushlog_%28tbpl%29 Update TBPL]
 * Create patches in buildbot-configs/mozilla/project_branches adding the project and if needed any custom mozconfig path or custom repo path
+** Example customization is turning on nightly updates, if this comes up you can copy the process from the UX branch see {{bug|642536}} for what is required wrt AUS
 * Do an update to branch and machines tables in graphs/sql/data.sql (branch 1.0 of this repo)
 * File a ServerOps bug (example {{bug|633663}}) to add graphserver entries until this is automated (see {{bug|627499}})
 * Add to self-serve ([https://wiki.mozilla.org/ReleaseEngineering/BuildAPI#Adding_branches instructions])
-== Old info which needs reviewing for relevance ==
+Once the above items are done and a few pushes have gone through without issue, close the bug - you're done!
+== Additional Steps For Adding Release Branches ==
 * File IT bugs:
-** to add nagios monitoring
+** to add Nagios monitoring on checks for file age in firefox/nightly/latest-$branch if required
 ** to add mxr indexing (release branches only - see [https://bugzilla.mozilla.org/show_bug.cgi?id=510495 bug 510495] for example)
-** to get rows added to graph server database:
-*** branches table for talos results (if applicable)
-*** machines table for the branch/platform's build/leak test results (if applicable)
 * File a Webtools/Socorro bug to add the new branch to vcsMappings:
 ** This allows devs to get source links for branch crash reports.
@@ Line 56: / Line 56: @@
 <pre>'hg.mozilla.org/REPO' => 'http://hg.mozilla.org/REPLACE_WITH_REPO/annotate/%(revision)s/%(file)s#l%(line)s'</pre>
-** mozilla (schedulerdb land)
+* Make sure to add mozconfigs for each platform!
-** <strike>mozilla2 (production-master)</strike>
-** <strike> mozilla2-staging (staging-master)</strike>
-** mobile configs if applicable
-** talos-r3 (talos-master, if applicable)
-** talos-staging-pool (talos-staging-master, if applicable)
-** Make sure to add mozconfigs for each platform!
-* Test staging patches - watch for mozconfigs, talos sendchanges working, file uploads to staging-stage
-* Push and enable production and staging patches
-* Schedule downtime and reconfig Talos
-* Set up Nagios monitoring on checks for file age in firefox/nightly/latest-$branch if required
 [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning:UnittestOptions Brief Note about Unittests]