Bugs set to fix released are reverted to fix committed
Bug #890161 reported by
Florian Boucault
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tarmac |
Expired
|
Low
|
Unassigned | ||
Bug Description
When merging a branch to which bugs are linked, tarmac sets these bugs to Fix Committed. That is a great feature. However, when one of these bugs is already set to Fix Released, tarmac should not revert them to Fix Committed.
| Changed in tarmac: | |
| importance: | Undecided → Low |
Revision history for this message
| dobey (dobey) wrote | #1 |
| Changed in tarmac: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in tarmac: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
How can a bug be Fix Released if developers are proposing branches that they have stated fixes the bug with bzr commit --fixes=lp:bug? It seems to me that the behavior is correct, as if new branches are fixing the bugs, then the fix can't already have been released.