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||<<Include(Xubuntu/Toolbox/Menu)>><<Include(Xubuntu/Toolbox/Banner)>>
|Line 3:||Line 4:|
|<<Include(Xubuntu/Toolbox/Menu)>><<Include(Xubuntu/Toolbox/Banner)>>||= Xubuntu Process Descriptions =|
|Line 5:||Line 6:|
|||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||||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.|
|Line 7:||Line 8:|
|== General processes ==|
|Line 8:||Line 10:|
|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]]|| * '''[[Xubuntu/Processes/ReleaseCycle|Release cycle]]'''
* '''[[Xubuntu/Processes/Community|Community processes]]'''
* Mailing list
* Project Lead nominee information
|Line 10:||Line 16:|
|Goals:||== Subteam processes ==|
|Line 12:||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!
| * '''[[Xubuntu/Processes/Development|Development]]'''
* Xubuntu packageset
* Xubuntu PPA's
* Package translations
* Updating the wiki and website
|Line 16:||Line 26:|
|== T minus 14 days ==||== Additional information ==|
|Line 18:||Line 28:|
| 1. Forward notifications of milestone freeze to firstname.lastname@example.org mailing list.
1. Insure freeze times are posted in #xubuntu-devel and email@example.com 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
Moving. This page has been prepared for moving to the Xubuntu Contributor Documentation. If you are about to make changes to this page, please consult the Xubuntu documentation team on #xubuntu-devel.
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
- Xubuntu PPA's
- Package translations
- 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: