BMO/new-version

Adding a new "rapid release" version to Firefox/Core/Thunderbird/Fennec

these steps use version 9 as an example.

when adding fields, create them as obsolete, set the values, and then clear the obsolete flag. occasionally bmo may timeout when adding a field; unfortunately this leaves the database in an unhealthy state. should this occur, the fix is to manually delete the row from the fielddefs table and try again.

it's important to wait 5 minutes between adding each field to give the slaves time to catch up. it's possible to break all the slaves by adding them too quickly (trust me, i've been there).

• create a tracking custom field:
  • name: cf_tracking_firefox9
  • description: tracking-firefox9
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "?", "+", "-"

• create a status custom field:
  • name: cf_status_firefox9
  • description: status-firefox9
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "unaffected", "affected", "fixed", "wontfix", "verified", "disabled", "verified disabled"

• create a tracking custom field:
  • name: cf_tracking_thunderbird9
  • description: tracking-thunderbird9
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "?", "+", "-"

• create a status custom field:
  • name: cf_status_thunderbird9
  • description: status-thunderbird9
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "unaffected", "affected", "fixed", "wontfix", "verified"

• Hide old custom field flags for previous (now released) versions (N-4) (remove from enter_bug checkbox, add to BMO/lib/Data.pm->cf_disabled_flags):
  • cf_tracking_firefox5
  • cf_status_firefox5
  • cf_tracking_thunderbird5
  • cf_status_thunderbird5

• add new milestones (yes, N+2 is correct):
  • Core: "mozilla11"
  • Firefox: "Firefox 11"
  • Firefox for Android: "Firefox 11"
  • Firefox for Metro: "Firefox 11"
  • MailNews Core: "Thunderbird 11.0"
  • Mozilla Localizations "mozilla11"
  • Mozilla Services: "mozilla11"
  • Other Applications: "mozilla11"
  • Testing: "mozilla11"
  • Thunderbird: "Thunderbird 11.0"
  • Toolkit: "mozilla11"

• move the --- milestone marker to between 8 and 9:
  • between mozilla8 and mozilla9
  • or between Firefox 8 and Firefox 9
  • or between Thunderbird 8 and Thunderbird 9

• add new versions:
  • Core: "9 Branch"
  • Firefox: "9 Branch"
  • Firefox for Android: "Firefox 9"
  • Firefox for Metro: "9 Branch"
  • MailNews Core: "9"
  • Testing: "9 Branch"
  • Thunderbird: "9"
  • Toolkit: "9 Branch"

• When adding new versions to "Firefox for Android", add the new versions to "Android Background Services" as well as they need to stay in sync.

• update cf_blocking_fennec (which is tracking-fennec in the UI) (add N+2, disable N-4):
  • add "11+"
  • disable "5+"

Adding a new "rapid release" version to ESR

• add a new point release:
  • edit the current tracking-firefox-esr17 and tracking-thunderbird-esr17 custom field values:
    • eg ".18+"

Adding a "rapid release" version to SeaMonkey

To determine the correct version number to add, check with a SeaMonkey owner first (Callek, or any member of the SeaMonkey Council).

These steps use version 2.8 as an example.

• create a tracking custom field:
  • name: cf_tracking_seamonkey28
  • description: tracking-seamonkey2.8
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "?", "+", "-"

• create a status custom field:
  • name: cf_status_seamonkey28
  • description: status-seamonkey2.8
  • type: drop down
  • can be set on bug creation: yes
  • values: "---", "unaffected", "affected", "fixed", "wontfix", "verified"

• Hide old custom field flags for previous (now released) versions (N-4) (remove from enter_bug checkbox, add to BMO/lib/Data.pm->cf_disabled_flags):
  • cf_tracking_seamonkey24
  • cf_status_seamonkey24

• add a new milestone "seamonkey2.8"
• move the --- milestone marker to between seamonkey2.7 and seamonkey2.8

• add a new version "SeaMonkey 2.6 Branch" (N-0.2)