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.

I will add some bugs and links to have examples.

• Create a reference image
  • Determine tool chain
    • TO BE COMPLETED
  • Must haves:
    • Nagios NRPE daemon
    • Puppet or OPSI client
    • post-clone automation (buildbot.tac generation and OPSI host key automation where appropriate)
    • 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
  • Update staging graph server
  • Builds should be succeeding
  • Unit tests should be passing, any oranges must be investigated
• Talos
  • TBD
• Release builds
  • Enable new platform in a staging release config
  • Update any release scripts that need to be made aware of the new platform.