Use bundles in merge directives to create branches
Bug #334090 reported by
Tim Penhey
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Aaron Bentley | ||
Bug Description
This has been disabled for 2.2.2, and needs tests to re-enable.
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in launchpad-bazaar: | |
| assignee: | nobody → abentley |
| importance: | Undecided → Medium |
| milestone: | none → 2.2.3 |
| status: | New → Triaged |
| Changed in launchpad-bazaar: | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
| Changed in launchpad-bazaar: | |
| milestone: | 2.2.3 → 2.2.4 |
| Changed in launchpad-code: | |
| status: | Fix Committed → Fix Released |
| visibility: | private → public |
To post a comment you must log in.
I think the main test for this should do the following:
1) Create the base branch for a new project using a bundle stored in the RF tree
2) Make that base branch the development focus to test stacking
3) Make a fake message using a second bundle stored in the RF tree
4) Process that message and confirm that a branch was created on disk stacked on the dev focus.
I talked with Gary about how to support non-automated testing of the incomming mail processor, and I have a solution that will require a little hacking :)