Upgrading minimum Go version?

[Curtis Hovey-Canonical]

On Mon, Nov 30, 2015 at 10:36 AM, John Meinel <john at arbash-meinel.com> wrote:
> Given how often people still use "--upload-tools" for things like private
> clouds (and is definitely the one used for local provider), I'd really worry
> about having a jujud on your local machine that wasn't built with the same
> toolchain as the one you get from "juju bootstrap" in other cases. Very easy
> to end up with hard to understand/reproduce bugs.

I share your concerns John.

We have seen several bugs marked invalid because the agent uploads is
essentially unknown origin because Juju is more than willing to fake a
version when uploading. There are also reports of Juju attempting to
build agents from source:
    https://bugs.launchpad.net/juju-core/+bug/1399606

We do want everyone using the agent in streams, which have a lot more
testing behind them. The agent (jujud) on users of the Juju stable PPA
is the same that was used to make streams. This is not true for users
of Ubuntu's packages, and we know Ubuntu can change its tool chain
between the time we create official agents and it builds its packages.
We do testing to certify they Ubuntu clients and agents are
functionally equivalent to those in the PPA and streams. As Ubuntu
Wily+ prefers system Go dev packages to the embedded go packages we
provide, Ubuntu's packages will contain more divergence than Trusty.
We are obligated to do on-demand testing to certify a change to a
system Go dev package.

Ideally, We would separate the jujud from juju-core package that
provides the client. Users don't get a jujud when they install a
client. Instead, Juju can get the desired agents from streams.

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