2011-09-19; CharlieKravetz; a process/checklist to assist in getting all the items done for Xubuntu releases
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|#title Xubuntu Release Process
|Line 5:||Line 3:|
|||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||||= Xubuntu Process Descriptions =
This page describes processes for Xubuntu development. All the processes and schedules should be used as a guidelines: This page ''mostly'' exists for us to document '''what we do''', not to tell us '''what to do'''. Minor issues and obvious shortcomings can be fixed without consulting, for larger-scale changes consult the team.
* '''[[Xubuntu/Processes/ReleaseCycle|Release cycle]]'''
* '''[[Xubuntu/Processes/Development|Development-related]]''' information
* Xubuntu packageset, package translations, ...
* '''[[Xubuntu/Processes/Daily|Process descriptions]]''' for other, more or less daily processes
* Meetings, mailing list moderation, ...
* '''[[Xubuntu/Processes/Maintenance|Regular maintenance]]''' of assets
* Updating the wiki and website
|Line 8:||Line 16:|
|To be carried out by: The Xubuntu Release Manager, with support from the Xubuntu Development Team and advice from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]||== Additional information ==|
|Line 10:||Line 18:|
* Ensure that all ISOs are suitable for release.
* This process should apply to alphas, betas, [[ReleaseCandidate|ReleaseCandidates]], final releases, and milestones.
* Ship it!
== T minus 14 days ==
1. Forward notifications of milestone freeze to email@example.com mailing list.
1. Insure freeze times are posted in #xubuntu-devel and firstname.lastname@example.org mailing list.
1. Freeze Day - notify developers of freeze and change topic in #xubuntu-devel.
== T minus 7 days ==
1. Request Xubuntu developers availability for milestone testing.
1. Review [[https://wiki.ubuntu.com/Xubuntu/Testing | testing pages]] to insure they are up to date.
1. Remind project lead to begin preparing release notes.
== T minus 5 days ==
* Testing should smoketest the images to insure they install.
== T minus 3 days ==
1. Testing begins on the images available.
* For alpha images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Short | short tests]].
* For beta, rc, and final images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Long | long tests]].
* All tests are recorded/tracked using the Ubuntu QA [[http://iso.qa.ubuntu.com/qatracker/build/xubuntu/all | ISO tracker]].
1. Coordinate all testing with Ubuntu QA in #ubuntu-testing.
1. Start the news article for the release; this is to be published on [[http://xubuntu.org | the website]] at the time of the release.
== T minus 1 day ==
1. Add release notes to the wiki.
* Alpha notes are combined with Ubuntu release notes at https://wiki.ubuntu.com/ReleaseName/TechnicalOverview .
* Beta and rc notes can be combined as alpha or, if significant changes were made should be separate under https://wiki.ubuntu.com/Xubuntu/ReleaseName/Milestone (example: https://wiki.ubuntu.com/Xubuntu/LucidLynx/Final).
== Release Day ==
1. Review the Technical Overview/Release Notes to insure everything is accurate.
1. Monitor for release announcement and PASS IT ON when announced.
* Publish news on the Xubuntu website.
* For the final release, insure the website download page is updated for the new release.
1. Review bugs to insure all bugs found during testing are listed at https://wiki.ubuntu.com/Xubuntu/Bugs/ReleaseName .
1. Update the [[https://wiki.ubuntu.com/Xubuntu/TeamReports | Team Report]].
1. Add milestone review to [[https://wiki.ubuntu.com/Xubuntu/Meetings | meeting agenda]].
* Reviewing as soon as possible helps to learn what we could have done better.
* This is also a great time to congratulate the team for a job well done.
== T plus 7 days ==
* Review this page and update it as needed for the next milestone/release period.
* Reviewing as soon as possible helps keep this as up to date as possible.
|In addition to the Xubuntu processes described below, there are several generic Ubuntu processes that are useful for the team and described elsewhere:
* [[FreezeExceptionProcess|Freeze exception process]] for getting to upload changes after a relevant freeze
* [[SponsorshipProcess|Sponsorship process]] for getting new package uploads in the archive
Xubuntu Process Descriptions
This page describes processes for Xubuntu development. All the processes and schedules should be used as a guidelines: This page mostly exists for us to document what we do, not to tell us what to do. Minor issues and obvious shortcomings can be fixed without consulting, for larger-scale changes consult the team.
- Xubuntu packageset, package translations, ...
Process descriptions for other, more or less daily processes
- Meetings, mailing list moderation, ...
Regular maintenance of assets
- Updating the wiki and website
In addition to the Xubuntu processes described below, there are several generic Ubuntu processes that are useful for the team and described elsewhere: