Differences between revisions 20 and 71 (spanning 51 versions)
← Revision 71 as of 2016-02-16 17:58:09
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|#title Xubuntu Processes||#REFRESH 5 http://docs.xubuntu.org/contributors/|
|Line 3:||Line 3:|
== Release Cycle ==
The release cycle consists of 5 more or less overlapping stages, which are:
||<tablestyle="width: 95%;" style="width: 20%;"> [[#Planning|Planning]] ||<style="width: 20%;"> [[#Developing|Developing]] ||<style="width: 20%;"> [[#Testing|Testing]] ||<style="width: 20%;"> [[#Releasing|Releasing]] ||<style="width: 20%;"> [[#Maintaining|Maintaining]] ||
=== Planning ===
Planning the release is conducted in three phases:
* Approving blueprints
* Finalizing specifications
In the brainstorming phase the contributors determine what they would like to work on during the release cycle, including proposals for changes in default applications. Anybody can items to the list. Settling on the goals in advance will make planning, focusing and estimating the likelihood for the features to be implemented easier.
After the brainstorming is over and before or on the Feature Definition Freeze day, the Xubuntu team will approve or reject the proposed blueprints. Any items with no assignee or rationale will be automatically rejected, but having them will not guarantee that the blueprint is approved. Other criteria include, but are not limited to: likelihood of getting the feature implemented, maintenance weight in the future, possible stability issues, influence on other blueprints, et cetera. The approved blueprints compose the roadmap for the release being developed.
After blueprints are approved, they should be finalized and detailed specifications should be written. These specifications should document the proposed changes and help guide the implementation. The Ubuntu freezes define the deadlines for implementation.
=== Developing ===
In addition to implementing the features and/or improvements set in the roadmap, there are a number of tasks which will occur during each release cycle:
* Xubuntu packages will be synced or merged with Debian as appropriate
* Bugs reported by users will be reviewed, fixed, and/or passed upstream
* Attempt to reduce our delta by pushing appropriate patches upstream
* Evaluate the seeds to ensure we are shipping the optimal software
* Work on improving and updating the Xubuntu documentation
=== Testing ===
Throughout the release cycle and even more so nearing the end, we will test Xubuntu to ensure that Xubuntu is a quality product that we are proud of. This includes testing that changes we have been making meet the release goals, work as expected, and do not cause regressions. Any tests run should be reported to the QA trackers. To read more about conducting tests and reporting them, refer to TESTING_WIKI.
The Xubuntu testing team will help ensure that when milestone ISOs are released, all tests are completed and results reported to the tracker. Xubuntu testers will also test the daily builds, upgrading through supported release paths and running the development version of Xubuntu on a daily basis to help detect problems. The most important goals for testing the daily images are simply to find as many bugs as possible and report them with sufficient detail to the tracker along with the ISO testing result.
The Xubuntu testing team also helps test applications that are included in Xubuntu and make sure sufficient amount of testing is made and results reported to the packages tracker. Additional testing should be conducted when a new default application is to be included in the next Xubuntu release.
=== Releasing ===
When it comes time to deploy a release (both milestones and final) several conditions must be met:
* Appropriate testing has been done on the image
* There are no known bugs which cause data loss or damage to hardware
* The image must not be oversized
* Xubuntu must be of sufficient quality that it would not damage Xubuntu's, Ubuntu's, or any of the other flavors' reputation/image.
When a release is made, the Xubuntu Release Team must follow the release process specified below. The release process ensures that the new release has sufficient release notes and release announcement and that all release-specific communication is updated to inform about the new release. Where needed, advice from the [[LP~ubuntu-release|Ubuntu release team]] should be asked for.
''' The Xubuntu release process '''
||<^> ''' 14 days before release ''' || Notifications of freezes <<BR>> Reminder to update the website FAQ (final release only) ||
||<^> ''' 7 days before release ''' || Gather people for milestone testing <<BR>> Start preparing release notes and release announcement ||
||<^> ''' 5 days before release ''' || Smoketest images ||
||<^> ''' 3 days before release ''' || Start milestone testing ||
||<^> ''' 1 day before release ''' || Review release notes ||
||<^> ''' Release day ''' || Mark images ready on the ISO tracker <<BR>> Publish release announcement and notes <<BR>> Update the website, IRC channel topics and social media outlets with new release information ||
||<^> ''' After release ''' || Update the developer wiki to next release (final release only) <<BR>> Review and update this page ||
=== Maintaining ===
After a release is made, bugs and problems are bound to be reported. The period between the release and the start of the next release cycle is the optimal time to perform Stable Release Updates (SRU) for major bugs as long as developers do not forget to fix the issue in the next release as well, once the repository opens. Once the next release cycle has started, primary focus will be on the next release and the severity/importance of the SRU candidates will be more important when it comes to deciding whether an SRU will be performed or not.
This page has been permanently moved to the Xubuntu Contributor Documentation. You will be redirected to the new location in 5 seconds.