On 02/11/13 03:32, Kapil Thangavelu wrote: > I'd suggest creating a bug per command (some already have extant bugs), > there's vastly differing amounts of work in them, and its easier to > track progress with appropriately sized tasks. ie kanban style cli api > is a story.
As discussed at the sprint, I think the best way to track with is with blueprint work items. I have registered a blueprint, linked the bug, and put Andrew's work in progress on the list. https://blueprints.launchpad.net/juju-core/+spec/t-cloud-juju-cli-api I also went through the photo I took of our big bit of paper and marked done those that were (although sync-tools seemed to be a bit edgy). As you take an item of work, prefix the work item with your launchpad id in square brackets (as the work item way), and mark it INPROGERSS. When it has landed, mark it DONE. That is all. Tim -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
