Juju Project Bug Triage Rules and Plan

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-09-24 22:27, Curtis Hovey-Canonical wrote:
> # Juju Project Bug Triage
> 
> Understanding when an issue must be addressed now, soon, or
> whenever an opportunity is presented.
> 
> 

I think this is a really nice summary and makes sense for us to
follow. It is close to a doc that we were roughly following earlier:

https://docs.google.com/a/canonical.com/document/d/1_XMfxKpySqy3bzM7oK3pYFWYvsll-6kMN85AM4kOG-o/edit#

But I think it has some bits that are more concrete about how we
should handle it.


One bit that we are missing is whether *all* development work should
be based on a bug. We're pretty close to it, but I know it isn't true
today. We do have Kanban vs Bugs, but neither is all that consistently
updated (as in by each person every day).

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJC0ywACgkQJdeBCYSNAAOykACeIPAxqufeiwcfjFM9lRlBsaP9
ZV4AnjIk3V2HkgH4Sx21Whz8Oidovs7i
=UhjE
-----END PGP SIGNATURE-----