Releasing stable, dev, and others

[Curtis Hovey-Canonical]

Gentlemen.

Juju-core 1.16.5 has one bug preventing us from doing a release. CI
has blessed  lp:juju-core/1.16 r1998. Do we want to defer the
"destroy-machine --force" bug?
    https://launchpad.net/juju-core/+milestone/1.16.5

Is there any reason not to backport the "http close=True" fix to
stable? Surely this bug affects several customers.
    https://bugs.launchpad.net/juju-core/+bug/1239558
I have verified we can increment the dependent libs. The patch applies
(with some corrections to dependencies.tsv).

Juju-core 1.17.0 still has regressions. HP is very broken, AWS has
intermittent bootstrap issues. Is it possible to focus effort on these
bugs to get a blessed revision? We have a good revision from Nov 4
(2071) but I don't think devs want to release a version that old.
    https://launchpad.net/juju-core/+milestone/1.17.0

These projects have never been released. I want to mark the bugs as
Fix Released since users must be using branches to work with the code.
I can create release tarballs if we think formal releases are demanded
by users.
    https://bugs.launchpad.net/goyaml/+bugs?search=Search&field.status=Fix+Committed
    https://bugs.launchpad.net/gomaasapi/+bugs?search=Search&field.status=Fix+Committed
    https://bugs.launchpad.net/goose/+bugs?search=Search&field.status=Fix+Committed

GWACL has a release, I think we want to cut another release to make
it's bugs Fix Released. Is anyone using the GWACL release? I suspect
the branch is used like most go projects.
    https://bugs.launchpad.net/gwacl/+bugs?search=Search&field.status=Fix+Committed

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui