Diff for "RoadMap"

Not logged in - Log In / Register

Differences between revisions 3 and 57 (spanning 54 versions)
Revision 3 as of 2009-11-27 17:30:59
Size: 1592
Editor: jml
Comment:
Revision 57 as of 2010-03-23 17:49:49
Size: 8650
Editor: jml
Comment: More detailed plans for second half of 2010
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
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. <<Anchor(roadmap)>>
= Roadmap =
Line 5: Line 6:
This page tries to present a rough roadmap as to how we'll do these.

= Bugs off Ubuntu =

== Bug heat ==

== Q&A on bugs ==

== Bug forwarding ==
|| 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 || || [[VersionFourDotO/Stories#story-2.3|End-to-end recipe building]]<<BR>> || [[https://dev.launchpad.net/VersionFourDotO/Stories#story-2.1|bzr-hg imports]] || Remove legacy "link project to source package" page<<BR>>''Consolidate linking code'' ||
|| [[https://edge.launchpad.net/launchpad-project/+milestone/10.02|Feb 2010]] || Convert to twisted, other cleanup || Solid delivery & polish of bug heat || List of bugs with patches<<BR>> Polish based on user feedback || || [[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]], [[https://bugs.edge.launchpad.net/launchpad-code/+bug/487357|bug 487357]] and [[https://bugs.edge.launchpad.net/launchpad-code/+bug/497645|bug 497645]] || [[https://bugs.edge.launchpad.net/launchpad-registry/+bug/487793|Portlet & page on distro page showing most important unlinked packages]]<<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.03|Mar 2010]] || Complete work on updating bugs, syncing comments, etc. || '''DONE''' || '''DONE''' || Beta delivery of Gnome [[https://dev.launchpad.net/VersionFourDotO/Stories#story-4.2.1|direct import]] || Daily build UI<<BR>>Polish of existing build UI || Incremental code imports (import the kernel!) || Q&A workflow for source package linking (Is it this project?)<<BR>>Update permissions logic to allow for better project bug tracker & branch gardening ||
|| [[https://edge.launchpad.net/launchpad-project/+milestone/10.04|Apr 2010]] || Add UI for bug syncing to LP, feature is done || bug-heat || patch-tracking || 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]] || Polish of daily build UI || code-imports || [[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.05|May 2010]] || Polish feature based on user feedback || bug-heat || patch-tracking || [[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-builds || code-imports || supporting-features ||
Line 16: Line 15:
= Daily builds = '''[[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.
Line 18: Line 17:
== Generic build infrastructure == You might also be interested in more general information on the [[VersionFourDotO|current Launchpad development cycle]].
Line 20: Line 19:
== Building source package branches with recipes == = Things that need to go onto the roadmap, somehow =
Line 22: Line 21:
== Full recipe interface ==

== Code imports for all major packages ==

 * bzr-svn support
 * bzr-hg support
 * [[https://bugs.edge.launchpad.net/launchpad-code/+bug/236973|bug 236973]] - the interval between launching a new code import job should be more flexible
 * [[https://bugs.edge.launchpad.net/launchpad-code/+bug/487357|bug 487357]] - the code import system calls requestMirror even if no revisions were imported
Many of these things don't fit into our [[VersionFourDotO/Themes|themes]], but we have to do to satisfy external obligations.
Line 33: Line 25:
 * Archive snapshots
Line 35: Line 28:
 * ARM support for PPAs
 * Branch privacy for distributions
Line 36: Line 31:
= The Road Ahead =
Line 37: Line 33:
= Translations integration = '''''This section is a draft. Don't rely on it.'''''
Line 39: Line 35:
'''XXX - fill this in.''' We're starting to get some idea of what we think we should do for the second half of 2010. We'll probably change our minds between now and June, but we'd like to start letting you know what we are thinking.
Line 41: Line 37:
= Supporting infrastructure = == Derivative distributions ==
Line 43: Line 39:
 * 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
We want to allow our commercial customers to create distributions on Launchpad that are derived from Ubuntu. We want them to have full archive building support, great bug filing workflows and full package branch support too.
Line 51: Line 41:
= Exceptions = == Privacy, permissions and notification ==
Line 53: Line 43:
These are things that don't fit into the above themes, but we have to do to satisfy external obligations.

== Archive snapshots ==
Privacy is a mess for Canonical's internal stakeholders, permissions are a mess for everyone and Launchpad sends way too much email. We need to decouple visibility from subscription and mutability from ownership and provide a clear, simple way to control who can read & write to what.
Line 59: Line 47:
== Branch privacy for distributions ==  * [[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]]

== Desktop integration ==

The Ubuntu desktop should be a wonderful platform for developers who want to write apps for the Ubuntu desktop. Launchpad is a core part of the way developers write applications for the Ubuntu desktop. It should be really easy for people to get started with Launchpad. In addition, we want to make sure that the Ubuntu One auth experience and the Launchpad auth experience line up well.

== Performance ==

Launchpad is too slow, make it faster.

<<Anchor(about)>>
= About this page =

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 ==

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 '''<<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.

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 [[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 &mdash; or make the roadmap more useful &mdash; contact the strategist or make a note on the page itself.

Roadmap

Month

Reliable Bug Syncing

Bug heat

Patch tracking

Translations

Daily Builds

Code imports

Supporting features

Dec 2009

Planning
Bug fixing

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

Improved through-put
Job-based system
Better error handling

Bug heat initial feature-complete UI

Badge for bugs with patches in listings

End-to-end recipe building

bzr-hg imports

Remove legacy "link project to source package" page
Consolidate linking code

Feb 2010

Convert to twisted, other cleanup

Solid delivery & polish of bug heat

List of bugs with patches
Polish based on user feedback

Once-off recipe build UI
Scalability work on build farm, more builds per day

Scaling work for code imports
bug 236973, bug 487357 and bug 497645

Portlet & page on distro page showing most important unlinked packages
Easier linking from source packages

Mar 2010

Complete work on updating bugs, syncing comments, etc.

DONE

DONE

Beta delivery of Gnome direct import

Daily build UI
Polish of existing build UI

Incremental code imports (import the kernel!)

Q&A workflow for source package linking (Is it this project?)
Update permissions logic to allow for better project bug tracker & branch gardening

Apr 2010

Add UI for bug syncing to LP, feature is done

bug-heat

patch-tracking

KDE direct import ability
Final delivery of GNOME direct import

Polish of daily build UI

code-imports

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

May 2010

Polish feature based on user feedback

bug-heat

patch-tracking

Translation import crowdsourcing
Automatic use of upstream translation imports

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.

Other

  • Archive snapshots
  • Online documentation for recipes
  • Building a community around daily builds
  • ARM support for PPAs
  • Branch privacy for distributions

The Road Ahead

This section is a draft. Don't rely on it.

We're starting to get some idea of what we think we should do for the second half of 2010. We'll probably change our minds between now and June, but we'd like to start letting you know what we are thinking.

Derivative distributions

We want to allow our commercial customers to create distributions on Launchpad that are derived from Ubuntu. We want them to have full archive building support, great bug filing workflows and full package branch support too.

Privacy, permissions and notification

Privacy is a mess for Canonical's internal stakeholders, permissions are a mess for everyone and Launchpad sends way too much email. We need to decouple visibility from subscription and mutability from ownership and provide a clear, simple way to control who can read & write to what.

Software Centre support

Desktop integration

The Ubuntu desktop should be a wonderful platform for developers who want to write apps for the Ubuntu desktop. Launchpad is a core part of the way developers write applications for the Ubuntu desktop. It should be really easy for people to get started with Launchpad. In addition, we want to make sure that the Ubuntu One auth experience and the Launchpad auth experience line up well.

Performance

Launchpad is too slow, make it faster.

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 (last edited 2012-06-26 19:57:16 by sinzui)