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:

do you want builds?

• which o.s.?
  • All o.s. or subset of linux, mac, win32, linux-arm
• incr-build-on-checkin? y/n
• nightlies? y/n
• Do you need l10n y/n?
  • Note: If you specifically need l10n, this currently needs dedicated machines, and significant longer setup.
  • all locales from m-c or a subset of locales?

want unittests?

• which o.s.?
  • All o.s. or subset of linux, mac, win32, linux-arm

want talos?

• which o.s.?
  • All o.s. or subset of linux, mac, win32
• fast talos or full talos or both?

(note: talos requires dedicated h/w, so need extra time to buy/install/configure/calibrate machines)

name of branch owner, who will:

• be doing periodic refreshes from m-c
• be contact person for misc setup questions
• decide when to land back project branch onto m-c
• decide when to terminate the project branch

timeline:

• when can we start project branch (any pre-req landings pending on m-c

preventing us from starting project branch?)

• expected life span of project branch - if known?

misc:

• need any changes to toolchain used in m-c?
• need any changes to the compile/link/repack steps used in m-c?
• preference on tinderbox waterfall name?
• preference on where to put builds on ftp.m.o?
  • used for places tinderbox-builds/my-project-branch, nightly/latest-my-project-branch/, or nightly/2008-08-08-08-my-project-branch/
• preference on name of project branch in hg?

any other info that might be helpful to us?

(note: RelEng will use this one tracking bug for all of the above setups, and RelEng will create dep bugs as needed.)