Upgrading minimum Go version?

[Martin Packman]

On 26/11/2015, Andrew Wilkins <andrew.wilkins at canonical.com> wrote:
> Hi (mostly Curtis),
>
> Is there a plan to bump the minimum Go version? Some of our dependencies do
> not build with Go 1.2. The LXD provider only builds with Go 1.3 (I think?),
> and I've got a PR up that updates the azure-sdk-for-go dependency, but it's
> blocked because the newer doesn't build with Go 1.2.

There are two issues with requiring a newer go version:

* The test suite needs to actually pass reliably with go 1.5
* How we get a version of juju that doesn't build with go 1.2 into
trusty needs resolving

With putting the newest juju into older Ubuntu releases, our strategy
so far has been to SRU back the same source as we put in the current
release, which we have a special allowance for. We cannot SRU a newer
go toolchain over the existing working 1.2 version, for hopefully
obvious reasons. Someone else may have better ideas, but I think that
leaves us basically three options:

* Stop putting new jujus in older ubuntus
* Use backports rather than -updates (this is what lxd does I believe)
* SRU a newer go toolchain to some alternative, juju only location

All of that is pretty big process changes that we can't just go ahead and do.

Test failures have been gradually tackled, we're down to a small-ish
set of issues causing reliable red results when we run unit tests on
vivid(1.3) and wily/xenial(1.5).

"TestContainerProvisionerStarted did not start"
http://reports.vapour.ws/releases/issue/5614b0e7749a5613c5aff2e0

"TestAPI2ResultError fails"
http://reports.vapour.ws/releases/issue/5640b28f749a562a3f656b39

"unexpected message panic"
http://reports.vapour.ws/releases/issue/55f34dfd749a561a11823b0b

Seem to be the ones I see most in recent test failures.

Martin