launchpad development|
Size: 2408
Comment:
|
Size: 2953
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| This section contains the [[http://www.agile-software-development.com/2008/04/writing-good-user-stories.html|story cards]] for the Launchpad Code team. Completed stories are moved to the [[VersionThreeDotO/Code/StoryCardsArchive]]. | This section contains the [[http://www.agile-software-development.com/2008/04/writing-good-user-stories.html|story cards]] for the Launchpad Code team. Completed stories are moved to the [[VersionThreeDotO/Code/StoryCardsArchive]]. Priorities are found on the [[VersionThreeDotO/Code|main code page]]. |
| Line 10: | Line 10: |
== Source Package Branches == |
|
| Line 33: | Line 31: |
| === Official source package branch for Distro Series === | == Official source package branch for Distro Series == |
| Line 41: | Line 39: |
| === Distribution source package branch listings === | == Distribution source package branch listings == |
| Line 59: | Line 57: |
| <<Anchor(script-scanner-emails)>> == Script to sent scanner generated revision emails == '''Story Points:''' ?? To stop the scanner generating diffs while scanning, the scanner should generate a new BranchJob to generate the diffs and send the revisions. '''Notes:''' * The scanner side of this is pretty simple. * Most likely the first BranchJob, so needs to factor in the BranchJob and Job classes. * Also need to factor in the time for the script that actually sends the email. |
Code User Stories
Blatently copied from the Registry user story page.
This section contains the story cards for the Launchpad Code team. Completed stories are moved to the VersionThreeDotO/Code/StoryCardsArchive. Priorities are found on the main code page.
Generic VFS for Codehosting
Story Points: 8
- As a Launchpad developer, I want to be able to do branch lookup in a single location so I can have arbitrary names for branches.
Notes:
- The codehosting system currently assumes branch naming semantics are tied to upstreams; this story card covers centralizing this code so it can be generalized to source package branches later.
Official source package branch for Distribution
Story Points: 5
- As a distribution vendor, I want to be able to specify a certain branch as being the trunk branch for a package in my distribution in order to allow any developer to easily fetch source for a package.
Official source package branch for Distro Series
Story Points: 5
- As a distribution vendor, I want to be able to specify a certain branch as being the focus branch for a package in a distro series so that developers working on that series know where to fetch the latest source branch for it from.
Distribution source package branch listings
Story Points: 3
- As a package maintainer, I want to be able to see what branches have been recorded for my source package in order to collaborate with their developers.
Needs estimating
These stories will be estimated in the weekly planning meeting.
Enabling Source Package Branches
Story Points: ??
- As a user I want to be able to associate a branch with a source package so I can use Bazaar to create and change source packages.
Script to sent scanner generated revision emails
Story Points: ??
To stop the scanner generating diffs while scanning, the scanner should generate a new BranchJob to generate the diffs and send the revisions.
Notes:
- The scanner side of this is pretty simple.
Most likely the first BranchJob, so needs to factor in the BranchJob and Job classes.
- Also need to factor in the time for the script that actually sends the email.
Example Story
Story Points: ??
- Description of the story
Notes:
- Any notes.
Needs definition
These stories are incomplete, not understood, and cannot be estimated.
