<div class="gmail_quote">On Thu, Sep 1, 2011 at 9:25 PM, Clint Byrum <span dir="ltr"><<a href="mailto:clint@ubuntu.com">clint@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I like this a lot, and I have to agree that there's a need for lightweight<br>
task tracking. Bugs don't associate to each other very well, so breaking<br>
one big bug up into multiple branches that ultimately lead to the bug<br>
being fixed isn't really obvious.<br></blockquote><div><br>Hrm - I totally agree about the bug associations, but for many multi-branch tasks, I don't see the need for multiple bugs that associate, when you can simply attach all the branches to the same bug like:<br>
<br><a href="https://bugs.launchpad.net/ubuntu-webcatalog/+bug/813346">https://bugs.launchpad.net/ubuntu-webcatalog/+bug/813346</a><br><br>That wouldn't be possible if you're creating a new bug for each branch that is pushed (rather than pushing branches which are already associated with a bug via `bzr commit --fixes lp:12345`.). So +1 to your suggestion below which allows either option :)<br>
<br>But yes, multiple-branches-per-bug doesn't help for larger features that are spread across multiple bugs (we currently manually tag the related bugs for that like you suggest).<br><br>-Michael<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Monty Taylor has been showing me OpenStack's integration of<br>
git+gerrit+launchpad, and one thing they do is have the "big things"<br>
in blueprints, and git branches/reviews tracked inside the blueprint<br>
whiteboard as tasks. This gives you one place to look at the status<br>
of something big that is in progress, without having to jump between<br>
multiple bugs that have no obvious relationship.<br>
<br>
Seems that a nice feature that would do the same thing for this workflow<br>
would be to attach these branches and newly created bugs to either a tag,<br>
or a blueprint, if one was specified. So..<br>
<br>
push-review ensemble-orchestra-integration<br>
<br>
If there was an existing --fixes bug, it would be attached to<br>
ensemble-orchestra-integration, and if there was no bug, then it would<br>
be created and attached. Alternatively it could work backwards, if the<br>
branch was connected to a blueprint already, then the bugs created would<br>
be attached to it, and vice-versa.<br>
<br>
The point is that just throwing a bug out there with no attachment to<br>
other artifacts is actually a pretty good first step. A nice refinement<br>
would be to help relate those bugs together with blueprints and/or tags.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Ensemble mailing list<br>
<a href="mailto:Ensemble@lists.ubuntu.com">Ensemble@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ensemble" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ensemble</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-<br>Michael Nelson<br><a href="http://liveandletlearn.net" target="_blank">http://liveandletlearn.net</a><br><a href="http://micknelson.wordpress.com/" target="_blank">http://micknelson.wordpress.com/</a><br>
<br>