launchpad development|
Size: 1573
Comment:
|
← Revision 3 as of 2011-11-02 03:55:29 ⇥
Size: 1735
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| ''Why are we doing this now?'' ''What value does this give our users? Which users?'' |
No real reason to do this now, aside from 'no time like the present'. This allows all of our users that make use of personal branches to have confidence that we are professional about handling their data. |
| Line 22: | Line 20: |
| ''Who really cares about this feature? When did you last talk to them?'' | Everyone, I hope! |
| Line 30: | Line 28: |
| '''As a ''' $PERSON<<BR>> '''I want ''' $FEATURE<<BR>> '''so that ''' $BENEFIT<<BR>> |
As a developer I want to trust Launchpad isn't treating my personal branches as junk so that I can have faith in them. |
| Line 34: | Line 32: |
| ''Have as many as you like. Group user stories together into meaningfully deliverable units. They'll be used as the driving elements of exploratory testing QA.'' | As a user I want to trust the data a developer has pushed into their personal branch so that ... |
| Line 40: | Line 40: |
| ''What MUST the new behaviour provide?'' | The ability to work with whatever the new name is (Be it +personal, p, or whatever) and legacy +junk URLs. |
| Line 43: | Line 43: |
A transition plan off +junk so we can stop supporting it at some $FUTURE_POINT. |
|
| Line 50: | Line 52: |
| == Subfeatures == ''Other LaunchpadEnhancementProposal``s that form a part of this one.'' |
The ability to move personal branches from the null pillar to a project. |
The purpose of this template is to help us get ReadyToCode on features or tricky bugs as quickly as possible. See also LaunchpadEnhancementProposalProcess.
The bits in italics are the bits that you should fill in. Delete the italic bits.
Talk to the product strategist soon after cutting a first draft of this document
Less Junk for personal branches
Currently, personal branches are of the form lp:~stevenk/+junk/foo.
Contact: StevenK
On Launchpad: https://bugs.launchpad.net/launchpad/+bug/147407
Rationale
No real reason to do this now, aside from 'no time like the present'. This allows all of our users that make use of personal branches to have confidence that we are professional about handling their data.
Stakeholders
Everyone, I hope!
User stories
$STORY_NAME
As a developer I want to trust Launchpad isn't treating my personal branches as junk so that I can have faith in them.
As a user I want to trust the data a developer has pushed into their personal branch so that ...
Constraints and Requirements
Must
The ability to work with whatever the new name is (Be it +personal, p, or whatever) and legacy +junk URLs.
Nice to have
A transition plan off +junk so we can stop supporting it at some $FUTURE_POINT.
Must not
What MUST it not do?
Out of scope
The ability to move personal branches from the null pillar to a project.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Put everything else here. Better out than in.
