launchpad development|
Size: 7433
Comment:
|
← Revision 77 as of 2012-06-26 19:57:16 ⇥
Size: 4348
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
<<Anchor(road-ahead)>> = The Road Ahead = This is exactly what we've been doing for the second half of 2010. We're behind schedule, but we're committed to doing these until we get them right. == Performance == Launchpad is too slow, make it faster. '''Status:''' We have driven down our hard timeout from 30s to 5s. 99.9% of all page renders happen in under 5s. == 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. See our [[LaunchpadEnhancementProposalProcess|LEPs]]: * [[LEP/BetterPrivacy]] = Longer-term ideas = These are ideas that we would like help from the community to implement. == Unified, consistent activity == At the moment, there is absolutely no way to look at a project in Launchpad and see what's happening. There are fragmented lists broken down by each component of Launchpad, but no clear view of activity. Likewise, there's no similar view for a person or a team. We would like to bring all of these views together to make "what's happening" extremely clear. Quite possibly, at the same time we'll review Launchpad's reward system. == Personal and project dashboards == Launchpad is about helping people make excellent software. The very least it can do with this is to make three things clear to its users: 1. What must you do? 1. What could you do? 1. What things are you waiting on from other people? It should be possible to see these things at a project level (e.g. "what do I have to do for this project?") and a personal level (e.g. "what do I have to do for all of my projects?"). == Better tools for QA and Release Management == Serious projects need to be able to manage bugs seriously. They need to be able to postpone bugs to future releases, see the rate of bug filing and bug fixing, burn down progress toward a release. == Consistent issue tracking == The blueprints part of Launchpad has been left behind. We should unify the bug & blueprints trackers without sacrificing the important distinctions between a defect, a specification and a plan for enhancement. == Archives for everyone! == PPAs have been really popular. However, tying them to a team or person isn't really good enough for many uses. In particular, upstream software projects often want to maintain their own archives. We should have archives associated with projects, rather than teams or people. <<Anchor(about)>> |
|
| Line 6: | Line 57: |
| == Using the page == | = Using the page = |
| Line 13: | Line 64: |
== 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. |
|
| Line 31: | Line 76: |
<<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]] || 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 || 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]], [[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''' || [[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 || 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 || translations || 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 || 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]]. = Things that need to go onto the roadmap, somehow = Many of these things don't fit into our [[VersionFourDotO/Themes|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 == * [[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]] == 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 is exactly what we've been doing for the second half of 2010. We're behind schedule, but we're committed to doing these until we get them right.
Performance
Launchpad is too slow, make it faster.
Status: We have driven down our hard timeout from 30s to 5s. 99.9% of all page renders happen in under 5s.
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.
See our LEPs:
Longer-term ideas
These are ideas that we would like help from the community to implement.
Unified, consistent activity
At the moment, there is absolutely no way to look at a project in Launchpad and see what's happening. There are fragmented lists broken down by each component of Launchpad, but no clear view of activity. Likewise, there's no similar view for a person or a team.
We would like to bring all of these views together to make "what's happening" extremely clear. Quite possibly, at the same time we'll review Launchpad's reward system.
Personal and project dashboards
Launchpad is about helping people make excellent software. The very least it can do with this is to make three things clear to its users:
- What must you do?
- What could you do?
- What things are you waiting on from other people?
It should be possible to see these things at a project level (e.g. "what do I have to do for this project?") and a personal level (e.g. "what do I have to do for all of my projects?").
Better tools for QA and Release Management
Serious projects need to be able to manage bugs seriously. They need to be able to postpone bugs to future releases, see the rate of bug filing and bug fixing, burn down progress toward a release.
Consistent issue tracking
The blueprints part of Launchpad has been left behind. We should unify the bug & blueprints trackers without sacrificing the important distinctions between a defect, a specification and a plan for enhancement.
Archives for everyone!
PPAs have been really popular. However, tying them to a team or person isn't really good enough for many uses. In particular, upstream software projects often want to maintain their own archives. We should have archives associated with projects, rather than teams or people.
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.
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.
