DevelopmentCycle
|
Size: 2623
Comment:
|
Size: 2002
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| ||'''Period'''||'''Description'''||'''Starts roughly at:'''||'''Ends roughly at:'''|| ||<#CCFFCC> [[UbuntuStudio/FeatureDefinition|Feature Definition]] || We plan for what features to add for the next release of Ubuntu Studio. || week 1 || week 5 - FeatureDefinitionFreeze|| |
||<#DFDFDF> '''Period'''||<#DFDFDF> '''Description'''||<#DFDFDF> '''Starts roughly at:'''||<#DFDFDF> '''Ends roughly at:'''|| ||<#CCFFCC> [[UbuntuStudio/DevEvents/FeatureDefinition|Feature Definition]] || We plan for what features to add for the next release of Ubuntu Studio. || week 1 || week 5 - FeatureDefinitionFreeze|| |
| Line 20: | Line 20: |
| ||<#FFCCCC> [[UbuntuStudio/DevEvents/DebianPackageTesting|Debian Package Testing]] || 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.<<BR>> All testing should be done within 1-3 weeks, so that there is enough time to report bugs, document them, and perhaps even fix them before the first beta release. || week 16 - DebianImportFreeze || week 19 || ||<#E47A7A> [[UbuntuStudio/DevEvents/BetaTesting|Beta Testing]] || At this point, everything should be done as far as features and artwork goes. <<BR>> We publish our Betas, so that our users can help us in catching bugs. || week 19 || week 25 - FinalFreeze || == Feature Specifications (blueprints) == Planning of feature changes is done primarily by the use of [[FeatureSpecifications|feature specifications]] in the form of blueprints at http://launchpad.net. See our [[UbuntuStudio/Blueprints|Blueprints page]] for an oversight of our active blueprints. |
||<#E49F9F> [[UbuntuStudio/DevEvents/Testing|Testing]] || Begins at DebianImportFreeze. Initially we test Debian packages for bugs. Once we hit feature freeze, we start doing beta testing. Later, UI testing. || week 16 || week 25 - FinalFreeze || ||<#E45F5F> [[UbuntuStudio/DevEvents/Release|Release]] || When we release, we need to make release announcements, adjust our website, etc. || week 26 || - || |
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. Initially we test Debian packages for bugs. Once we hit feature freeze, we start doing beta testing. Later, UI testing. |
week 16 |
week 25 - FinalFreeze |
|
When we release, we need to make release announcements, adjust our website, etc. |
week 26 |
- |
UbuntuStudio/DevelopmentCycle (last edited 2016-01-29 08:52:30 by 83)