Developing juju against a known Go release

[roger peppe]

i think we should build and test against as many Go versions as
possible, back to some specified
release. in particular, i think that juju should work against both tip
and 1.0.(2? 3?).

for gofmt, i think we should standardise on the latest released Go
version. (1.0.3 currently).


On 26 November 2012 10:39, David Cheney <david.cheney at canonical.com> wrote:
> Hello,
>
> Recently, CL 6845096, was proposed to work around functional differences
> between Go 1.0 and Go trunk. I think it is probably time to decide on a
> version of Go that we all use. Note: this doesn't mean we all have to keep
> using this version for ever, just that we use the _same_ version. Bare in
> mind that this version will also be the build-dep for the release package.
>
> With that in mind, the candidates are
>
> * golang-go package from precise (identical in quantal). This is a version
> closely approximating 1.0.2. There are some unfortunate bugs in the net/http
> package, but I think goamz works around those.
>
> * golang-trunk (from gustavo's PPA), which fixes so many bugs it is not
> funny, including some horrid timeout bugs that bradfitz and I fixed over
> thanksgiving.
>
> * go 1.0.3 (probably from our own PPA), which fixed some net/http bugs, but
> backported others.
>
> As the nominator, I abstain from casting a vote, but will do so in the event
> of a tie.
>
> Dave
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev