• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Later Stories

Patch forwarding

Story A

• As a non-core developer using Launchpad and Bazaar,
  I want to give my fix to upstream in a way they can merge it using their tools,
  so that we both can use our tools we're comfortable with when collaborating

  • Notes:

    • do we need a story about submitting a patch contained in a source package?
    • point the upstream developers either to a URL they can merge from directly, or a page containing the diff, information about the patch, and instructions about how to merge the fix using their tools. E.g., if we have an import of a git branch, there should be instructions for how to merge the fix using git.
    • push notifications about fixes ready for review through bug syncing

Story B

• As an Ubuntu developer,
  I want to see which patches in my package that need to be sent upstream,
  so that others can benefit from my work

  • Notes:

    • Helps the Ubuntu developer to see what needs to be done to reduce the delta to upstream, and to see how he can contribute to the upstream project

Story C

• As an Ubuntu developer,
  I want to see which patches that have been sent upstream have been merged,
  so that I can politely remind upstream to merge my work.

  • Notes:

    • This may be used for the Ubuntu developer to make sure that his work actually gets merged, and is not forgotten about.
    • This will also make it possible for upstream, so see whether there are patches in Launchpad for them.

Story D

• As a drive-by upstream contributor (John)
  I want to point upstream to my fix in Launchpad
  So that my fix can be easily merged upstream.

Story E

• As a drive-by upsteam contributor (John)
  I want the upstream bug tracker to be notified when my fix is ready in LP
  So they can merge my fix

Story F

• As a developer
  I want bug followers to be notified when my linked branch is ready for review
  So that they can try out and review my fix

Story J

• An an Ubuntu user
  I want to be told only when a bug is believed to be fixed
  So that I can test the fix (without lots of "noise" mail)

  • Notes: Needs to know how to test (eg. "in Karmic" or "in this PPA")

Story K

• As a person who gets too much mail
  I want to be able to selectively turn off some Launchpad mails
  So that I can get less mail.

Story L

• As an irritable Ubuntu user
  I want to stop _all_ mail LP
  So that I don't feel spammed.

Story M

• As John the coder
  I want to get mail when anything (in a product, in a distro, in a team, etc) changes
  So that I can use my preferred client and search/read the data offline.

Story N

XXX - not "later", but actually out of scope for Launchpad.

• As someone who makes Ubuntu packages (whether distro or PPA),
  I want to upload my package to Launchpad and have it published both for Ubuntu and Debian
  So that it's easier for Debian to test my improvements (e.g., bug fixes that haven't been sent upstream yet)

  • Notes: Bug #188564 ("Build also packages for Debian in PPA's")

Story O

• As the driver of an Ubuntu release
  I want to link all packages in the release to upstream releases
  so that I can choose the best version to include in Ubuntu.

Story P

XXX - jml doesn't understand this.

• As Kara (the gcc maint in Ubuntu)
  I need to apply a mechanichal patch to 70 Gnome packages for a new gcc version
  So that I can prepare them for shipment in Ubuntu.

Story R

XXX - jml doesn't understand this.

• As John, the Ubuntu maintainer of Gwivver
  I need to coordinate UI changes in the current release
  So that address Ubuntu users' issues with this application

Story S

• As the MySQL release manager
  I need to talk to the Ubuntu release manager
  So that we can coordinate our next release cycle

Story T

• As the Ubuntu release manager
  I need to like to quickly distinguish people who are important to me
  So that focus on the right issues from incoming requests

Story U

• As Bill, the OEM manager for Dell
  I want to help my external, secret translations team that I hired for our upcoming secret release create package translations
  So that I can ship our product in 20 languages

Story V

• As Bill, the OEM manager for Dell
  I need to send our translations upstream from our previous release
  So that stop maintaining our translation and reduce costs

Story W

• As as 3rd party contract developer for Dell
  I need to maintain my specific versions of upstream changes
  So that I can add them to Dell's product with current versions of packages

Story X

• As Bill, the OEM manager for Dell
  I need to help my hired, secret coders for our upcoming secret release code
  customize and continue to follow trunk So that I can ship customized and up to date versions of our packages

Story Y

• As Bill, the OEM manager for Dell
  I need to send our patches upstream from our previous release
  So that stop maintaining our patches and reduce costs

Story Z

• As someone who wants to interact with an upstream project
  I want to get everything about that project in Launchpad
  so that I don't have to learn new tools; and that I can take advantage of any network effects that Launchpad provides and that I don't have to context switch

Story AA

• As a package maintainer
  I want to sync the full history of Debian packages to Ubuntu
  so that the burden of maintaining these packages becomes lighter

Story AB

• As Bill the OEM manager,
  I want my QA team to test and give feedback as fast as possible for my distribution maitained in a PPA
  So that I produce higher quality release for my hardware.