Diff for "RoadMap"

Not logged in - Log In / Register

Differences between revisions 31 and 35 (spanning 4 versions)
Revision 31 as of 2010-01-05 03:29:08
Size: 5372
Editor: jml
Comment:
Revision 35 as of 2010-01-05 04:03:06
Size: 5600
Editor: jml
Comment: Use a macro, rather than link to the URL itself.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Introduction = ## 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)>>'''.

==
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 18:
== How complete is it? ==
Line 12: Line 21:

== Questions? ==

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

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

Infrastructure work

Refactoring of build system
Recipe schema
Recipe UI design

bzr-svn imports

Bug-free package / project linking experience

Jan 2010

Q&A UI widget
Second bug Q&A question (steps to reproduce?)

Bug heat initial feature-complete UI

List of bugs with patches
Badge for bugs with patches in listings

Beta delivery of Gnome direct import

End-to-end recipe building

bzr-hg imports

Portlet & page on distro page showing most important unlinked packages
Initial Q&A workflow for source package linking (Is it this project?)
Easier linking from source packages

Feb 2010

Full delivery of Q&A on bug pages
Initial cut of exposing bug readiness in listings

Solid delivery & polish of bug heat

DONE

KDE direct import ability
Final delivery of GNOME direct import

Recipe workflow UI

Scaling work for code imports
bug 236973 and bug 487357

Q&A for source package linking

Mar 2010

Full delivery of bug readiness in listings

DONE

DONE

Translation import crowdsourcing
Automatic use of upstream translation imports

Building from recipes with private branches

Drive-through project creation
User-visible indication of project completeness (bugs 204119 and 490593)

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

RoadMap (last edited 2012-06-26 19:57:16 by sinzui)