| 2006-10-10 07:41:31 |
John A Meinel |
bug |
|
|
added bug |
| 2006-10-10 17:30:51 |
David Allouche |
launchpad: statusexplanation |
|
|
|
| 2006-10-17 20:21:02 |
David Allouche |
bug |
|
|
assigned to malone (upstream) |
| 2006-10-18 16:45:18 |
David Allouche |
malone: status |
Unconfirmed |
Confirmed |
|
| 2006-10-18 16:45:18 |
David Allouche |
malone: importance |
Undecided |
Medium |
|
| 2006-10-18 16:45:18 |
David Allouche |
malone: statusexplanation |
|
|
|
| 2006-10-18 16:45:28 |
David Allouche |
launchpad-bazaar: status |
Unconfirmed |
Confirmed |
|
| 2006-10-18 16:45:28 |
David Allouche |
launchpad-bazaar: importance |
Undecided |
Medium |
|
| 2008-01-16 11:21:29 |
Matthew Paul Thomas |
description |
If you create a new Bazaar branch when fixing a bug, there are a lot of extra steps/clicks necessary when you need to mark the bug as fixed and the branch as merged.
I realize there is some discussion of ways to do this automatically, but that can be error prone, and until it is implemented it still can be useful to make the manual process more streamlined.
These are the steps needed to close the bug:
1) Go to the bug page
2) Open up the bug status, and mark it as fix released, possibly add a version number, and message, and submit.
3) Click on the associate branch link
4) Click on the link to the actual branch page
5) Click on the link to change the branch status
6) select 'merged' from the list, and submit.
One possibly improvement would be to get rid of the 'associated branch' page, and instead fold that into the actual branch page. So if a branch is associated with multiple bugs, it could get multiple sub pages. Similar to how Bugs associated with multiple upstreams are handled.
Also, when setting the overall branch status, the actual branch status is sort of hidden in a small square on the left, which is not clickable. And to change the status is on an entirely different page from a link which is far away. Also, you can't change the status on the details page, which means there are multiple pages for handling the information about a branch.
Understandable some are more stable information, (branch description, etc) versus more variable (current branch status). But these should be unified. |
If you create a new Bazaar branch when fixing a bug, there are a lot of extra steps/clicks necessary when you need to mark the bug as fixed and the branch as merged.
I realize there is some discussion of ways to do this automatically, but that can be error prone, and until it is implemented it still can be useful to make the manual process more streamlined.
These are the steps needed to close the bug:
1) Go to the bug page
2) Open up the bug status, and mark it as fix released, possibly add a version number, and message, and submit.
3) Click on the associate branch link
4) Click on the link to the actual branch page
5) Click on the link to change the branch status
6) select 'merged' from the list, and submit.
One possibly improvement would be to get rid of the 'associated branch' page, and instead fold that into the actual branch page. So if a branch is associated with multiple bugs, it could get multiple sub pages. Similar to how Bugs associated with multiple upstreams are handled.
Also, when setting the overall branch status, the actual branch status is sort of hidden in a small square on the left, which is not clickable. And to change the status is on an entirely different page from a link which is far away. Also, you can't change the status on the details page, which means there are multiple pages for handling the information about a branch.
Understandable some are more stable information, (branch description, etc) versus more variable (current branch status). But these should be unified.
(For registering the branch in the first place, see bug 113218.) |
|
| 2008-11-14 00:06:20 |
Jonathan Lange |
launchpad-bazaar: assignee |
|
jml |
|
| 2008-11-14 00:06:20 |
Jonathan Lange |
launchpad-bazaar: statusexplanation |
|
I should read over this and figure out what's still missing. |
|
| 2008-11-14 01:00:33 |
Jonathan Lange |
description |
If you create a new Bazaar branch when fixing a bug, there are a lot of extra steps/clicks necessary when you need to mark the bug as fixed and the branch as merged.
I realize there is some discussion of ways to do this automatically, but that can be error prone, and until it is implemented it still can be useful to make the manual process more streamlined.
These are the steps needed to close the bug:
1) Go to the bug page
2) Open up the bug status, and mark it as fix released, possibly add a version number, and message, and submit.
3) Click on the associate branch link
4) Click on the link to the actual branch page
5) Click on the link to change the branch status
6) select 'merged' from the list, and submit.
One possibly improvement would be to get rid of the 'associated branch' page, and instead fold that into the actual branch page. So if a branch is associated with multiple bugs, it could get multiple sub pages. Similar to how Bugs associated with multiple upstreams are handled.
Also, when setting the overall branch status, the actual branch status is sort of hidden in a small square on the left, which is not clickable. And to change the status is on an entirely different page from a link which is far away. Also, you can't change the status on the details page, which means there are multiple pages for handling the information about a branch.
Understandable some are more stable information, (branch description, etc) versus more variable (current branch status). But these should be unified.
(For registering the branch in the first place, see bug 113218.) |
If you create a new Bazaar branch when fixing a bug, there are a lot of extra steps/clicks necessary when you need to mark the bug as fixed and the branch as merged.
I realize there is some discussion of ways to do this automatically, but that can be error prone, and until it is implemented it still can be useful to make the manual process more streamlined.
These are the steps needed to close the bug:
1) Go to the bug page
2) Open up the bug status, and mark it as fix released, possibly add a version number, and message, and submit.
3) Click on the associate branch link
4) Click on the link to the actual branch page
5) Click on the link to change the branch status
6) select 'merged' from the list, and submit.
One possibly improvement would be to get rid of the 'associated branch' page, and instead fold that into the actual branch page. So if a branch is associated with multiple bugs, it could get multiple sub pages. Similar to how Bugs associated with multiple upstreams are handled.
(For registering the branch in the first place, see bug 113218.) |
|
| 2008-11-14 01:02:14 |
Jonathan Lange |
launchpad-bazaar: status |
Confirmed |
Triaged |
|
| 2008-11-14 01:02:14 |
Jonathan Lange |
launchpad-bazaar: assignee |
jml |
|
|
| 2008-11-14 01:02:14 |
Jonathan Lange |
launchpad-bazaar: importance |
Medium |
Low |
|
| 2008-11-14 01:02:14 |
Jonathan Lange |
launchpad-bazaar: statusexplanation |
I should read over this and figure out what's still missing. |
AIUI, this bug is about providing an easy way to say, "this branch fixed this bug and it has now landed on trunk". Although it would be nice to have, we are focusing on more automatic ways of achieving the same. |
|
| 2008-11-14 01:02:43 |
Jonathan Lange |
malone: status |
Confirmed |
Invalid |
|
| 2008-11-14 01:02:43 |
Jonathan Lange |
malone: statusexplanation |
|
We only need to track this on launchpad-bazaar |
|
| 2009-02-05 04:34:39 |
Jonathan Lange |
launchpad-bazaar: importance |
Low |
High |
|
| 2009-02-05 04:34:39 |
Jonathan Lange |
launchpad-bazaar: statusexplanation |
AIUI, this bug is about providing an easy way to say, "this branch fixed this bug and it has now landed on trunk". Although it would be nice to have, we are focusing on more automatic ways of achieving the same. |
|
|
| 2010-08-25 21:21:31 |
Paul Hummer |
launchpad-code: status |
Triaged |
Fix Released |
|
