ReleaseEngineering/Official Platform Support Checklist

These are the steps that will have to be taken in order to officially support a new platform. They don't exactly have to happen in this order but it more or less follows a sequential order and some steps can be followed in parallel.

DISCLAIMER: This page is NOT guaranteed to contain 100% of the needs for all platforms. Use this page a guideline. Skip things that don't make sense for a given platform and do additional things that do make sense for it.

• File a tracking bug - bug 512489
• Create a reference image - bug 519074
  • Determine tool chain
    • TO BE COMPLETED
  • Must haves:
    • Nagios NRPE daemon - Installing nagios for L64
    • Puppet (example) or OPSI client
    • post-clone automation (buildbot.tac generation and OPSI host key automation where appropriate) - (TODO: point to some documentation)
    • Staging SSH keys
  • Document OS installation and all subsequent changes on a ReferencePlatforms page
• Generate a build and pass it to QA
• Deploy ref image to slaves
  • File IT bugs:
    • Clone/image machines
    • Nagios checks
• Create mozconfig(s). Standard mozconfigs for Desktop Firefox at the time of writing are: debug, nightly (aka opt), release, xulrunner)
• Testing/baking on staging
  • Enable standard jobs in staging buildbot configs (normal and debug builds)
  • Make sure codesighs run (not for windows) - bug 547056
  • Update staging graph server - bug 547029
  • Builds should be succeeding
  • Unit tests should be passing, any oranges must be investigated
• Talos
  • Ref-image
  • Nagios
  • Puppet or OPSI
  • Add slaves to talos-pool and graph server db - bug 530680
• Release builds - bug 548605
  • Enable the new platform on a staging release configuration file
  • Update any release scripts that need to be made aware of the new platform. (which scripts?)
• Breakpad support - bug 464750 (might not be the easiest example)
• TBPL support - bug 532560