-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-12-12 22:16, Curtis Hovey-Canonical wrote: > On Thu, Dec 12, 2013 at 1:09 PM, Curtis Hovey-Canonical > <[email protected]> wrote: >> We close bugs when we know we have delivered a fix to the >> affected users. Our practice of targeting to milestones/releases >> is a little misleading if we assume the bug was in the previous >> release. Some bugs only affect users of trunk, such as developers >> and testers. > > Another facet of releases is that we do devel and stable releases. > We mark bugs as fix released, but we advise users to not use the > fix in production. Surely this is confusing. The fix is not really > released until 1.18.0. >
I think that is a fair point, and I see 2 possible ways of doing it. One is that we could add a "stable release" series and add a bug target for that series for things that are important fixes relative to the last stable release. Or we could only mark things Fix Released when it goes to a stable release. Although, if we have it in a dev release someone *could* get access to it if it was critically important. (vs having to build from source.) But the fact that we aren't guaranteeing they'll be able to upgrade away from a dev release means that may not be sufficient to ever point them to. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Cygwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKqigoACgkQJdeBCYSNAAMnawCgxSRceqPpZ4VpEFScWfaU5+4U tasAn1NCTrahk2CEQ9mURTw+ZnDVieAT =azAD -----END PGP SIGNATURE----- -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
