ManagingBlueprints
Differences between revisions 2 and 8 (spanning 6 versions)
|
Size: 622
Comment:
|
Size: 748
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(UbuntuStudio/Navigation/Header)>> <<Include(UbuntuStudio/Navigation/CoreSideBar)> * One blueprint for each binary package (including meta packages) * One blueprint for each non-package project (docs, artwork, PR, etc) Main projects: * Installer Image * Website * Documentation (user and developer) -------- [[UbuntuStudio/BlueprintsTemplate|Release Blueprints Template]] - used when planning for next release |
|
| Line 6: | Line 21: |
| == Managing Workitems == | ---- |
| Line 8: | Line 23: |
| View every workitem as a suggestion? View each change to the source as reversable? How to process each workitem (suggestion): * Create a workitem, based on a bug or a feature request * Research the effects of implementing the work item, and publish on mail list * If there are no objections, or improvements to the work item, implement it |
CategoryUbuntuStudioPlanning CategoryUbuntuStudio |
<<Include(UbuntuStudio/Navigation/CoreSideBar)>
- One blueprint for each binary package (including meta packages)
- One blueprint for each non-package project (docs, artwork, PR, etc)
Main projects:
- Installer Image
- Website
- Documentation (user and developer)
Release Blueprints Template - used when planning for next release
- Creating a topic (done by a Ubuntu Developer)
- Creating blueprints (done by the Ubuntu Studio developer in charge of blueprints)
- Creating workitems (done by any Ubuntu Studio developer)
- Managing workitems (DONE, POSTPONED, etc)
UbuntuStudio/ManagingBlueprints (last edited 2015-04-26 16:27:35 by h-141-65)