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,
  • Incremental-build-on-checkin? y/N
  • Are en-US builds enough, with no l10n? Y/n
    • If you 'must' have l10n, do you need all locales from parent branch or just a subset of locales?
  • NOTE: we cant yet provide nightly updates for project branches like this. We're working on this, but its not possible yet.

• Do you want unittests?
  • All o.s. or subset of: WinXP, Win7, 10.5, 10.6, fedora12, fedora12-64, maemo4, maemo5gtk, maemo5qt (with android and 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:
  • 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

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

• File IT bug to create hg repo

• File IT bug to add nagios monitoring

• File IT bug to get rows added to graph server database:
  • branches table for talos results (if applicable)
  • machines table for leak test results (if applicable)

• Create patches in buildbot-configs for:
  • mozilla2 (production-master)
  • mozilla2-staging (staging-master)
  • mobile configs if applicable
  • talos-pool (talos-master, if applicable)
  • talos-staging-pool (talos-staging-master, if applicable)
  • Make sure to include mozconfigs!

• Test staging patches

• 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