5082
Comment:
|
7122
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
'''DRAFT -- don't believe a word this says''' | ## page was renamed from VersionFourDotO/Roadmap = About this page = |
Line 3: | Line 4: |
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]]. == Using the page == |
Line 7: | Line 10: |
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. | 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 '''<<Action(subscribe, subscribe now)>>'''. We've crammed as many links as we could find into the page. These links themselves often link to other things. Follow these links and explore the dark and dangerous world of Launchpad development. == 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. |
Line 11: | Line 20: |
== How complete is it? == |
|
Line 12: | Line 23: |
Also, this is mostly about Canonical-sponsored development. Community contributors are welcome to join in, but are just as welcome to scratch whatever itches them. == Questions? == |
|
Line 15: | Line 30: |
|| 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]]) || |
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. |
Line 21: | Line 32: |
<<Anchor(roadmap)>> = Roadmap = || Month || '''[[Bugs/ReliableBugSyncing|Reliable Bug Syncing]]''' || '''[[Bugs/BugHeat|Bug heat]]''' || '''[[Bugs/PatchTracking|Patch tracking]]''' || '''[[https://dev.launchpad.net/VersionFourDotO/Stories#Translations|Translations]]''' || '''[[VersionFourDotO/Stories#story-2a|Daily Builds]]''' || '''[[VersionFourDotO/Stories#story-2.1|Code imports]]''' || '''Supporting features''' || || [[https://edge.launchpad.net/launchpad-project/+milestone/3.1.12|Dec 2009]] || ''Planning''<<BR>>[[https://bugs.edge.launchpad.net/malone/+bugs?field.milestone:list=22619&field.tag=story-reliable-bug-syncing|Bug fixing]] || ''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]] || [[https://lpstats.canonical.com/graphs/BugWatchUncheckedOutdated/|Improved through-put]]<<BR>>''Job-based system''<<BR>>''Better error handling'' || Bug heat initial feature-complete UI || Badge for bugs with patches in listings || Beta delivery of Gnome [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.1|direct import]] || [[VersionFourDotO/Stories#story-2.3|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]] || Controls and status info for bug watches || Solid delivery & polish of bug heat || List of bugs with patches<<BR>> Polish based on user feedback || 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]] || [[VersionFourDotO/Stories#story-2.11|Once-off recipe build UI]]<<BR>>''Scalability work on build farm, more builds per day'' || 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]] || '''DONE''' || '''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]] || Daily build UI<<BR>>Polish of existing build UI || || [[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]]) || || [[https://edge.launchpad.net/launchpad-project/+milestone/10.04|Apr 2010]] || reliable-bug-syncing || bug-heat || patch-tracking || translations || Polish of daily build UI || code-imports || supporting-features || || [[https://edge.launchpad.net/launchpad-project/+milestone/10.05|May 2010]] || reliable-bug-syncing || bug-heat || patch-tracking || translations || daily-builds || code-imports || supporting-features || '''[[Bugs/BugQ&A|Bug Q&A]] (also [[VersionFourDotO/Stories#story-1.6|a story]]) has been postponed, due to the higher urgency of getting reliable upstream bug syncing.''' First question for bug Q&A (does this affect you?) is done. You might also be interested in more general information on the [[VersionFourDotO|current Launchpad development cycle]]. |
|
Line 46: | Line 72: |
= Meta = * Link to stories * Highlight missing stories * https://dev.launchpad.net/Bugs -- link up to this * Remove the warning |
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.
We've crammed as many links as we could find into the page. These links themselves often link to other things. Follow these links and explore the dark and dangerous world of Launchpad development.
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.
Also, this is mostly about Canonical-sponsored development. Community contributors are welcome to join in, but are just as welcome to scratch whatever itches them.
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 |
Supporting features |
||||||
Planning |
Algorithm design |
Patches separate from attachments on bug page |
Infrastructure work |
Refactoring of build system |
Bug-free package / project linking experience |
||
Improved through-put |
Bug heat initial feature-complete UI |
Badge for bugs with patches in listings |
Beta delivery of Gnome direct import |
Portlet & page on distro page showing most important unlinked packages |
|||
Controls and status info for bug watches |
Solid delivery & polish of bug heat |
List of bugs with patches |
KDE direct import ability |
Once-off recipe build UI |
Scaling work for code imports |
Q&A for source package linking |
|
DONE |
DONE |
DONE |
Translation import crowdsourcing |
Daily build UI |
|
Drive-through project creation |
|
reliable-bug-syncing |
bug-heat |
patch-tracking |
translations |
Polish of daily build UI |
code-imports |
supporting-features |
|
reliable-bug-syncing |
bug-heat |
patch-tracking |
translations |
daily-builds |
code-imports |
supporting-features |
Bug Q&A (also a story) has been postponed, due to the higher urgency of getting reliable upstream bug syncing. First question for bug Q&A (does this affect you?) is done.
You might also be interested in more general information on the current Launchpad development cycle.
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