1277
Comment:
|
5592
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
'''DRAFT -- don't believe a word this says''' | = About this page = |
Line 3: | Line 3: |
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 is a rough guide on what we're doing over the next few months as part of our [[VersionFourDotO|current development cycle]]. |
Line 5: | Line 5: |
This page tries to present a rough roadmap as to how we'll do these. | == Using the page == |
Line 7: | Line 7: |
= Bugs off Ubuntu = | 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. |
Line 9: | Line 9: |
== Bug heat == | We intend to maintain this page for future planning cycles of Launchpad, so if you are at all interested in having a say in Launchpad development [[https://dev.launchpad.net/VersionFourDotO/Roadmap?action=subscribe|subscribe now]]. |
Line 11: | Line 11: |
== Q&A on bugs == | == The dates == |
Line 13: | Line 13: |
== Bug forwarding == | "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. == How complete is it? == Sometimes we'll do cool stuff and won't note it down here. Follow our blog for things like that. == Questions? == This page is maintained by the [[https://launchpad.net/~jml|Launchpad Product Strategist]]. If you have any questions, contact the strategist, or begin a discussion on the [[https://launchpad.net/~launchpad-users|Launchpad users mailing list]]. This page is, and probably always will be a work-in-progress. If our plans change, we'll try to make sure you hear about it. If you have any ideas on how we can do that better — or make the roadmap more useful — contact the strategist or make a note on the page itself. = Roadmap = || Month || '''Bug Q&A''' || '''Bug heat''' || '''Patch tracking''' || '''[[https://dev.launchpad.net/VersionFourDotO/Stories#Translations|Translations]]''' || '''Daily Builds''' || '''Code imports''' || '''Supporting features''' || || Dec 2009 || First question for bug Q&A (does this affect you?) || ''Algorithm design'' || Patches separate from attachments on bug page<<BR>> || ''Infrastructure work'' || Refactoring of build system<<BR>> Recipe schema<<BR>> Recipe UI design || [[https://dev.launchpad.net/VersionFourDotO/Stories#story-2.1|bzr-svn imports]] || Bug-free package / project linking experience || || [[https://edge.launchpad.net/launchpad-project/+milestone/10.01|Jan 2010]] || Q&A UI widget<<BR>> Second bug Q&A question (steps to reproduce?) || Bug heat initial feature-complete UI || List of bugs with patches<<BR>> Badge for bugs with patches in listings<<BR>> || Beta delivery of Gnome [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.1|direct import]] || End-to-end recipe building<<BR>> || [[https://dev.launchpad.net/VersionFourDotO/Stories#story-2.1|bzr-hg imports]] || [[https://bugs.edge.launchpad.net/launchpad-registry/+bug/487793|Portlet & page on distro page showing most important unlinked packages]]<<BR>>Initial Q&A workflow for source package linking (Is it this project?)<<BR>>[[https://blueprints.edge.launchpad.net/launchpad-registry/+spec/ubuntu-link-to-upstream|Easier linking from source packages]] || || [[https://edge.launchpad.net/launchpad-project/+milestone/10.02|Feb 2010]] || Full delivery of Q&A on bug pages<<BR>> Initial cut of exposing bug readiness in listings || Solid delivery & polish of bug heat || '''DONE''' || KDE [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.1|direct import]] ability<<BR>> Final delivery of GNOME [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.1|direct import]] || Recipe workflow UI<<BR>> || Scaling work for code imports<<BR>>[[https://bugs.edge.launchpad.net/launchpad-code/+bug/236973|bug 236973]] and [[https://bugs.edge.launchpad.net/launchpad-code/+bug/487357|bug 487357]] || Q&A for source package linking || || [[https://edge.launchpad.net/launchpad-project/+milestone/10.03|Mar 2010]] || Full delivery of bug readiness in listings || '''DONE''' || '''DONE''' || [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.0|Translation import crowdsourcing]]<<BR>> [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.2|Automatic use of upstream translation imports]] || Building from recipes with private branches || || [[https://blueprints.edge.launchpad.net/launchpad-registry/+spec/upstream-link-to-ubuntu|Drive-through project creation]]<<BR>>User-visible indication of project completeness (bugs [[https://bugs.edge.launchpad.net/launchpad-registry/+bug/204119|204119]] and [[https://bugs.edge.launchpad.net/launchpad-registry/+bug/490593|490593]]) || |
Line 16: | Line 36: |
= Daily builds = | = Things that need to go onto the roadmap, somehow = |
Line 18: | Line 38: |
== Generic build infrastructure == | Many of these things don't fit into our [[VersionFourDotO/Themes|themes]], but we have to do to satisfy external obligations. |
Line 20: | Line 40: |
== Building source package branches with recipes == | == Supporting infrastructure == |
Line 22: | Line 42: |
== Full recipe interface == | * UI for selecting an archive * Crowd-sourcing * code import maintenance * bug import maintenance |
Line 24: | Line 47: |
== Code imports for all major packages == | == Software Centre support == |
Line 26: | Line 49: |
* bzr-svn support * bzr-hg support |
* [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-software-center-repository-based-index|Archive index]] * [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-ratings-and-reviews-in-software-center|Ratings and reviews]] * [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-user-contributed-metadata-for-software-center|User-contributed metadata]] |
Line 31: | Line 55: |
* Archive snapshots | |
Line 33: | Line 58: |
* ARM support for PPAs * Branch privacy for distributions |
|
Line 34: | Line 61: |
= Meta = | |
Line 35: | Line 63: |
= 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 == |
* Link to stories * Highlight missing stories * https://dev.launchpad.net/Bugs -- link up to this |
About this page
This page is a rough guide on what we're doing over the next few months as part of our current development cycle.
Using the page
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.
We intend to maintain this page for future planning cycles of Launchpad, so if you are at all interested in having a say in Launchpad development subscribe now.
The dates
"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.
How complete is it?
Sometimes we'll do cool stuff and won't note it down here. Follow our blog for things like that.
Questions?
This page is maintained by the Launchpad Product Strategist. If you have any questions, contact the strategist, or begin a discussion on the Launchpad users mailing list.
This page is, and probably always will be a work-in-progress. If our plans change, we'll try to make sure you hear about it. If you have any ideas on how we can do that better — or make the roadmap more useful — contact the strategist or make a note on the page itself.
Roadmap
Month |
Bug Q&A |
Bug heat |
Patch tracking |
Daily Builds |
Code imports |
Supporting features |
|
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 |
Bug-free package / project linking experience |
|
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 |
Portlet & page on distro page showing most important unlinked packages |
||
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 |
Q&A for source package linking |
|
Full delivery of bug readiness in listings |
DONE |
DONE |
Translation import crowdsourcing |
Building from recipes with private branches |
|
Drive-through project creation |
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
- Crowd-sourcing
- code import maintenance
- bug import maintenance
Software Centre support
Other
- Archive snapshots
- Online documentation for recipes
- Building a community around daily builds
- ARM support for PPAs
- Branch privacy for distributions
Meta
- Link to stories
- Highlight missing stories
https://dev.launchpad.net/Bugs -- link up to this