On 08/09/2013 01:00 PM, Chris Evich wrote: Sorry for chiming in later :(
Thanks, though I'm really interested in HOW we should manage the TODO's. To be clear, my assumption is that once someone picks up a TODO item (by creating a pull-request) then the TODO item will be removed (whatever the system). So, starting new work will involve checking both the TODO list and current pull requests (as you've done here).
I'm thinking that, since the issues can be linked, the TODO item is closed only when all the work, including pushing the pull request. As the pull request will be linked to the TODO item, it's easy to see the state before closing. Anyone would just have to search through TODO items to figure out whether anyone is working on that particular task.
Also note: Pull requests to next do not preclude multiple people collaborating. It's fine to send pull requests to eachother (i.e. against someone else's topic branch). When accepted it will just become part of the original pull request against next. Anyway, my question remains, does anyone have any ideas for alternatives to what I wrote below? How about other problems or solutions I did not mention?
Other than I don't think we should close TODO items until the work is complete, I do like the idea of multiple people colaborating, pull requests to maintainer's branches and all that.
Cheers, Lucas _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
