closing bugs in goose and gwacl
John Arbash Meinel
john at arbash-meinel.com
Wed Oct 30 04:04:36 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013-10-29 22:08, Curtis Hovey-Canonical wrote:
> There are many Fix Committed bugs in goose and gwacl. Since we
> don't go regular releases of these libraries, their bugs remain
> open for a long time.
>
> Do we want to do regular releases? Do we consider their use in a
> release stable juju-core to be Fix Released? Do we care about
> releases at all since Go prefers branch tips, not releases?
>
Both of those projects are stable enough at this point that we could
probably move to a slow-releases model. (We should depend on released
versions of them, and when we make fixes, we make a release.) Though
at *this* point, it feels like a lot of busy work when we don't have
any other 3rd parties depending on them.
If it isn't particularly hard to do a release, I think just releasing
them when we do a juju-core release would be reasonable.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJwhVQACgkQJdeBCYSNAAPKNQCcCsX2HcIfBVyvXhVUsc0W3Aw2
OfQAnRVQo/varUbdEJkt4ruN1tooAJ5o
=nsVl
-----END PGP SIGNATURE-----
More information about the Juju-dev
mailing list