When I clicked on Fix Available, and hit "update", thinking that it would update the bug status to Fix Available, hopefully with some helpful default text, instead nothing happened.
When I clicked on Fix Available and typed some text, and hit "update", again the bug status wasn't changed,
and a bit of information was added. So I guess that is what bug-branches are.
this seemed to me to mean everything would be taken care of: "changes the State of the bug-branch relationship to Fix Available". But I clearly didn't understand what a bug-branch relationship was. So clarifying what _doesn't_ happen would help. The rest of that section seems designed to do so, but uses different terms like "close a bug" which I took to mean another subtlety. So I guess --fixes _creates_ the "bug-branch relationship".
I was also confused by the documentation and behavior.
I didn't even notice the information added to the bug and the trunk page after pushing a commit that used --fixes.
E.g. to /bugs.edge. launchpad. net/electionaud its/+bug/ 278330 electionaudits/ trunk (New) - Fix Available "
https:/
this was added:
"~nealmcb/
but no email was sent to bug subscribers about that major piece of news.
When I clicked on Fix Available, and hit "update", thinking that it would update the bug status to Fix Available, hopefully with some helpful default text, instead nothing happened.
When I clicked on Fix Available and typed some text, and hit "update", again the bug status wasn't changed,
and a bit of information was added. So I guess that is what bug-branches are.
I don't see this doc, referred to earlier:
http:// doc.bazaar- vcs.org/ latest/ en/user- guide/bug_ trackers. html
But I was confused by what I did find in http:// doc.bazaar- vcs.org/ bzr.1.6/ en/tutorials/ using_bazaar_ with_launchpad. html#changing- the-state- in-launchpad- while-committin g-in-bazaar
this seemed to me to mean everything would be taken care of: "changes the State of the bug-branch relationship to Fix Available". But I clearly didn't understand what a bug-branch relationship was. So clarifying what _doesn't_ happen would help. The rest of that section seems designed to do so, but uses different terms like "close a bug" which I took to mean another subtlety. So I guess --fixes _creates_ the "bug-branch relationship".