FeatureDefinition
|
Size: 1629
Comment:
|
Size: 1638
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 26: | Line 26: |
| * If a feature breaks something in Ubuntu, it may be disapproved by the ubuntustudio-core team. Also, it will most probably be disapproved later by Ubuntu devs anyway. | * If a feature spec will break something in Ubuntu, it may be disapproved by the ubuntustudio-core team. Also, it will most probably be disapproved later by Ubuntu devs anyway. |
In the beginning of a development we do feature definition.
Tasks during feature definition
week 1-4 |
discuss on the mail list and irc channels on feature additions |
week 4-5 |
finalize blueprints at around week 4, and have them approved before FeatureDefinitionFreeze |
Making 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.
Suggesting changes
Anyone can suggest a feature change/addition. But, to make it a reality, someone needs to implement it. Usually it is the same person that makes the suggestion.
Creating Blueprints
Blueprints should in first hand be created by members in one of the restricted Ubuntu Studio dev teams (ubuntustudio-core, ubuntustudio-dev, ubuntustudio-art, etc).
Approving Feature Specs
- If a feature spec is not objected, it is automatically approved.
- If a feature spec will break something in Ubuntu, it may be disapproved by the ubuntustudio-core team. Also, it will most probably be disapproved later by Ubuntu devs anyway.
- If a feature is objected by anyone, it needs to be discussed within the community. ubuntustudio-core team has last say - whose responsibility lies in upholding the quality and integrity of Ubuntu Studio.
UbuntuStudio/DevEvents/FeatureDefinition (last edited 2014-05-08 09:42:06 by 83)