launchpad development|
Size: 4905
Comment:
|
Size: 4910
Comment: Dec -> December
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| 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". Each month is linked to the Launchpad release milestone for that date, so you can see what we're ''actually'' doing. | 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 December 2009". Each month is linked to the Launchpad release milestone for that date, so you can see what we're ''actually'' doing. |
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.
Use this page to keep track of what we are planning on doing, and when. If you think "I'd like to know what to expect of Launchpad over the coming months", then this is the page to follow.
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 December 2009". Each month is linked to the Launchpad release milestone for that date, so you can see what we're actually doing.
Note that the dates here aren't actually commitments, they are just our best guesses.
Sometimes we'll do cool stuff and won't note it down here. Follow our blog for things like that.
Month |
Bug Q&A |
Bug heat |
Patch tracking |
Daily Builds |
Code imports |
|
Dec 2009 |
First question for bug Q&A (does this affect you?) |
Algorithm design |
Patches separate from attachments on bug page |
Infrastructure work |
Refactoring of build system |
|
Q&A UI widget |
Bug heat initial feature-complete UI |
List of bugs with patches |
Beta delivery of Gnome direct import |
End-to-end recipe building |
||
Full delivery of Q&A on bug pages |
Solid delivery & polish of bug heat |
DONE |
KDE direct import ability |
Recipe workflow UI |
Scaling work for code imports |
|
Full delivery of bug readiness in listings |
DONE |
DONE |
Translation import crowdsourcing |
Building from recipes with private branches |
|
Things that need to go onto the roadmap, somehow
Many of these things don't fit into our themes, but we have to do to satisfy external obligations.
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
Archive snapshots
Software Centre support
Branch privacy for distributions
ARM support for PPAs
Other
- Online documentation for recipes
- Building a community around daily builds
More notes
jml / sinzui roadmap conversation, 2009-12-22
Dec 2009
- Bug-free package / project linking experience
Jan 2010
Portlet & page on distro page showing most important unlinked packages (bug 487793)
Start of Q&A workflow for source package linking (Is it this project?)
- Easier linking from source packages
https://blueprints.edge.launchpad.net/launchpad-registry/+spec/ubuntu-link-to-upstream
Feb 2010
- User-visible indication of project completeness (bugs 204119 and 490593)
Q&A for source package linking (Is it this source package?)
https://blueprints.edge.launchpad.net/launchpad-registry/+spec/upstream-link-to-ubuntu
Mar 2010
- Drive-through project creation
Meta
- Link to stories
- Highlight missing stories
https://dev.launchpad.net/Bugs -- link up to this
- Remove the warning
