-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-04 0:45, Tim Penhey wrote: > 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.
I thought we had a blueprint already, but I guess the discussion was just done in the Bitesize session. > > 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). Can you at least link the image to the blueprint so we can see the Size information for each item? > > 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 > Thanks, John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Cygwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ3iO4ACgkQJdeBCYSNAAOsYQCcCqeWrUaw1hR+/LU5Y45eNnoC HY0An0uh583fwzkto12Q6gNf5CdjIK0D =LEWw -----END PGP SIGNATURE----- -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
