launchpad development|
Size: 2377
Comment:
|
Size: 2401
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| || Dec 2009 || design for bug heat<<BR>> design for Q&A || || Refactoring of build system<<BR>> Recipe schema<<BR>> Recipe UI design || bzr-svn imports || || | || Dec 2009 || design for bug heat<<BR>> design for Q&A || ''Infrastructure work'' || Refactoring of build system<<BR>> Recipe schema<<BR>> Recipe UI design || bzr-svn imports || || |
DRAFT -- don't believe a word this says
There are three major areas of development for Launchpad 4.0: getting bugs off Ubuntu, enabling the daily builds story and tighter cross-project collaboration in translations.
This page tries to present a rough roadmap as to how we'll do these. "Dec 2009" means "targeted to the rollout at the end of Dec 2009".
Month |
Bugs |
Translations |
Daily Builds |
Code imports |
Exceptions |
Dec 2009 |
design for bug heat |
Infrastructure work |
Refactoring of build system |
bzr-svn imports |
|
Jan 2010 |
bug heat initial implementation |
|
End-to-end recipe building |
bzr-hg imports |
|
Feb 2010 |
Solid delivery of bug heat |
|
Recipe workflow UI |
Scaling work for code imports |
|
Mar 2010 |
|
|
Building from recipes with private branches |
|
|
Apr 2010 |
|
|
|
|
|
May 2010 |
|
|
|
|
|
Other
- Online documentation for recipes
- Building a community around daily builds
Translations integration
XXX - fill this in.
Supporting infrastructure
- UI for selecting an archive
- Improved package / product linking
- JIT registration of projects for creating imports
- Crowd-sourcing
- code import maintenance
- bug import maintenance
- project / package linking
Exceptions
These are things that don't fit into the above themes, but we have to do to satisfy external obligations.
Archive snapshots
Software Centre support
Branch privacy for distributions
Meta
- Link to stories
- Only include user-visible features
- Fill in the blanks
- Add some stuff on how to use, why this exists etc.
