ReleaseEngineering:ProjectBranchPlanning

If you want a new project branch, please file one bug in mozilla.org/ReleaseEngineering, and put the questions below, and their answers in the bug to help us get started:

NOTE: RelEng will use this one tracking bug for all of the above setups, and will create dependent bugs with different groups in Mozilla as needed.

• Name of hg repo for this branch (relative to hg.mozilla.com)
  • NOTE: this name will be used for all things related to the branch, tinderbox, tbpl, ftp locations, etc.
  • Has a bug already been filed to create the repo?
  • Name of parent branch?

• Do you want builds?
  • All o.s. or subset of linux32, linux64, osx10.5, osx10.6, win32, win64
  • Incremental-build-on-checkin? y/N
  • Nightly builds? Y/n
    • Nightly updates? y/N

• Do you want unittests?
  • All o.s. or subset of: WinXP, Win7, 10.5, 10.6, fedora12, fedora12-64, maemo4, maemo5gtk, maemo5qt, android (with Win7x64 coming soon).

• Do you need mobile builds?
  • All o.s. or subset of linux-i686, macosx-i686, maemo4, maemo5gtk, maemo5qt
  • Incremental-build-on-checkin? y/N

• Do you want talos?
  • Do you need talos on Tiger?
  • All o.s. or subset of Talos platforms?

• Name of the contact person for this branch who will:
  • Be doing periodic refreshes from parent
  • Be contact person for misc setup questions
  • Decide when to land back project branch onto parent
  • Decide when to terminate the project branch

• Timeline:
  • Is this branch is needed for a specific hard calendar deadline? (we typically can do this in 2 weeks, and we will notify you if we think we'll miss that)
  • For changes in schedule, or status checks, please ping in bug.
  • Approx expected life span of project branch - if known?

• Additional requests:
  • Need any changes to toolchain used in parent branch?
  • Need any changes to the compile/link/repack steps used in parent branch?
  • Do you expect to create any releases from this project branch?
    • NOTE: Currently we do not have nightly/alpha/beta/release updates on these project branches.
  • Any other info that might be helpful to us?

Release Engineering Checklist

note --- all new branches should be created in buildbot-0.8.0 branch of buildbot-configs using scheduler db

• Create tinderbox page for the branch to report to and file bug for tbpl

• File IT bugs:
  • to create hg repo
  • to add nagios monitoring
  • to add mxr indexing (release branches only - see 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.
  • Ask for this:

'hg.mozilla.org/REPO' => 'http://hg.mozilla.org/REPLACE_WITH_REPO/annotate/%(revision)s/%(file)s#l%(line)s'

• Create patches in buildbot-configs for:
  • mozilla (schedulerdb land)
  • mozilla2 (production-master)
  • mozilla2-staging (staging-master)
  • 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

Brief Note about Unittests