Firefox3.1/3.5

The version number of Shiretoko will be moved from Firefox 3.1 to Firefox 3.5 as per the proposed plan. We'll co-ordinate details here.

Please note: Each of these items are simply proposed right now and we might find other ways to make similar changes.

Project Outline

• change the version number of Shiretoko from 3.1 to 3.5
• announce a set change-over date, and have all affected systems change on that date
• monitor for problems after the change
• no change to the version number of Gecko (it will remain 1.9.1)
• no change to the version number of previous alpha/beta releases

Roll-out Timeline

The following timeline based on Firefox 3.1b3 shipping the week of March 8.

(Missing from this list is MDC which has already completed their switchover.)

Anytime

• AUS
  • land and deploy patch from bug 481478

March 16

• announce tree downtime (1.9.1-only) for March 17

March 17

• build team
  • (morning) downtime; move tinderboxen from Firefox3.1 tree to Firefox 3.5 tree
  • change version number on 1.9.1 to 3.5b4pre
  • change version number on mozilla-central to 3.6a1pre
  • update nagios checks for builds
• other system changes
  • mstange updates tinderboxpushlog
  • dolske updates istg
• amo
  • rename maxVer 3.1b4pre to 3.5b4pre
  • rename maxVer 3.2a1pre to 3.6a1pre
• bugzilla
  • rename blocking-firefox3.1 flag to blocking-firefox3.5
  • rename target milestones
  • server-side (justdave or reed?): update all charts
    • [list goes here]
• wiki
  • update main queries listed on wiki (platform pages too)
  • move major Firefox3.1 wiki pages
• crash-stats
  • everything listed below

April 6

• support
  • rename all docs from 3.1 to 3.5

Affected Systems

tinderbox/build

(lead: bhearsum)

• redirect Firefox3.1 -> Firefox3.5
  • requires at least five hours downtime (win32 Talos is the long pole)
  • need to up the version number on branch to 3.5b4pre
  • need to up the version number on trunk to 3.6a1pre
• several systems pull data using the tree=Firefox3.1 URL
  • tinderboxpushlog, isthetreegreen, ??
• update nagios checks for nightlies (branch and trunk)

bugzilla

(lead: ss, working with justdave/reed)

• rename blocking-firefox3.1 to blocking-firefox3.5
• rename target milestones (beta 4 and later)
• update queries
• update charts (server side?)

AUS

(lead: morgamic)

• For nightlies, update config-mapping between versions and snippet directories - bug 481478

mozilla add-ons

(lead: osunick)

• change available maxVer and minVer targets
  • AMO allows you to target trunk builds e.g. 3.2a1pre which will now be 3.6a1pre.
• automatically migrate 3.1 maxVers to 3.5?
  • Yes, there are > 10k extensions on AMO. An automated bump would be more efficient compared to 10,000 developers logging in and moving their maxVersion settings manually through the UI.

crash-stats

(lead: ss, aking)

• add 3.5b4pre version number
• add mtbf report for 3.5b4pre
• add byurl report for 3.5b4pre
• symbols need no changes

MDC

(lead: sheppy)

• move 3.1 docs to 3.5
• setup any needed redirects
• template changes as needed
• version strings all over the site need to be fixed

SUMO

(lead: djst)

• move 3.1 docs to 3.5
• make sure 3.1 is sniffed as 3.5
• fix software references
  • "Show contents customized for"
  • KB article categories

Messaging

(lead: ss)

• MDC: Should have a doc describing changes
• User-facing: Need doc for users on "whatsnew" or something similar

Pentaho

• don't need to aggregate 3.1/3.5 numbers