Ubuntu Studio release procedure

This checklist is for the Ubuntu Studio team members to push out an new Ubuntu Studio release.

Please use this etherpad to do the release planning.

14 days before release

1. The Ubuntu Studio Development Team should ensure that all the bugs that were targetted to the milestone of the release (if any) is fixed. If there are remaining bugs, fix it before the archive is frozen.

When Ubuntu Studio candidate builds of the release gets on to the ISO Tracker

2. The assigned person from the Ubuntu Studio Public Relations and Support Team responsible for calls for testing (currently Howard Chan (smartboyhw)) should call for testers to test the release using ubuntustudio.org, mailing lists (ubuntu-quality, ubuntu-studio-devel and ubuntu-studio-users), Google+ and other social mediae.

3. The Ubuntu Studio Testing Team should start test the images to see if there are any bugs and report them through the ISO QA Tracker.

Release day

Please follow the steps one by one

4. The Ubuntu Studio Release Team should update the release notes located in a page in the Ubuntu Wiki and make sure it is fully correct.

5. The Ubuntu Studio Release team should check whether the images in the ISO QA Tracker is critical bug-free and all the testcases have been completed.

If it is and that the team's majority agrees that the release is ready, one of the team members should mark the images as ready in the ISO QA Tracker.

If there is a critical bug, members of the Ubuntu Studio Development Team must immediately fix the bug and upload it to the archive. Then the Ubuntu Studio Release Team should ask the Ubuntu Release team for a respin of the images (or if the team has privileges they can do it themselves). And then the team should ping any tester from the Ubuntu Studio Testing Team in #ubuntustudio on Freenode IRC to test the images.

If the testcases hadn't been completed please contact the testers in #ubuntustudio-devel on Freenode IRC to test the images immediately

For i386 images and amd64 images emergency testing contact Len Ovenwerks (Len-nb) and Howard Chan (smartboyhw) respectively. The members of the Ubuntu Studio Core Team should also be pinged.

6. The assigned person from the Ubuntu Studio Public Relations and Support Team responsible for release annoucements (currently Scott Lavender (slavender/scott-work) should post out an annoucement of the release to the mailing lists (ubuntu-studio-users and ubuntu-studio-devel), ubuntustudio.org, Google+, Twitter, Facebook and other social mediae.

7. The members of the Ubuntu Studio Public Relations and Support Team and/or the Ubuntu Studio Website Team team members should update all the download links on ubuntustudio.org and the wiki and the community documentation to accomodate the latest release.

8. The members of the IRC Ubuntu Studio Ops should update the channel topics of #ubuntustudio and #ubuntustudio-devel channels on Freenode IRC.

1 to 2 weeks after release

9. The assigned person from the Ubuntu Studio Public Relations and Support Team (currently Kaj Ailomaa (zequence)) should post a call for contributors to the mailing lists (ubuntu-studio-users and ubuntu-studio-devel), ubuntustudio.org, Google+, Twitter, Facebook and other social mediae.