DevelopmentCycle
Development Cycle
Currently, development is done in 6 months periods, correlating with our releases. Usually Ubuntu Studio is released in April and October of every year. LTS (long term support release) is released every 2 years, and development for that is done over a two years period.
Release Schedule
To keep track of important dates, we use a development release schedule. See our current developmemt release schedule for an oversight of important dates.
Important Events
A development cycle is divided into different periods, following the important events that occur.
Period |
Description |
Starts roughly at: |
Ends roughly at: |
We plan for what features to add for the next release of Ubuntu Studio. |
week 1 |
week 5 - FeatureDefinitionFreeze |
|
The period during which we add features to Ubuntu Studio - application development, changing settings, artwork, etc. |
week 5 - FeatureDefinitionFreeze |
feature addition ends: week 18 - FeatureFreeze |
|
Begins at DebianImportFreeze. We test all Debian imported packages in the Ubuntu Studio package set for bugs, so we have a chance of fixing them - preferably fixing them upstream in Debian, and then resyncing. |
week 16 - DebianImportFreeze |
week 19 |
|
At this point, everything should be done as far as features and artwork goes. |
week 19 |
week 25 - FinalFreeze |
Feature Specifications (blueprints)
Planning of feature changes is done primarily by the use of feature specifications in the form of blueprints at http://launchpad.net. See our Blueprints page for an oversight of our active blueprints.