Go 1.8 Beta 1 is released

[Chris Broadfoot]

Hello gophers,

We have just released go1.8beta1, a beta version of Go 1.8.

It is cut from the master branch at the revision tagged go1.8beta1.

There are no known problems or regressions.

Please try running production workloads and your unit tests with the new version.

It is important that we find bugs *before* issuing a release candidate.

The release candidate is planned for the first week of January.

Your help in testing this beta is invaluable.

Report any problems using the issue tracker:

    https://golang.org/issue/new

You can download binary and source distributions from the usual place:

    https://golang.org/dl/#go1.8beta1

To find out what has changed in Go 1.8, read the draft release notes:

    https://beta.golang.org/doc/go1.8

Documentation for Go 1.8 is available at:

    https://beta.golang.org/

Our goal is to release the final version of Go 1.8 on February 1st.

Cheers,

Chris

[Zlatko Čalušić]

Hello,

and thanks for another great Go release!

I have just one question, and it's not specific to this beta, but all Go betas and rc-s.

I compile Go from repository like this:

cd $HOME/src/go.googlesource.com/go
git checkout -f master
git clean -fdx
git pull --ff-only
git checkout -f go1.8beta1
cd src && make.bash

The resulting binary unfortunately is not labeled as go1.8beta1, but instead:

go version devel +41908a5 Thu Dec 1 02:54:21 2016 +0000 linux/amd64

What follows next is that various Go software, where developers decided to explicitely test for Go version (and of course don't deal well with devel versions) fails to compile. One example is gopherjs, it's uncompilable with this beta version, unless I manually edit the source and remove gratuitous checks.

The question is, how do I persuade the compiled beta to report version as go1.8beta1?

I have a feeling there should be a simple recipe for that, which would better the chance of successful compile for various picky projects. :)

Thanks for any hint you can provide.

Regards,

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
Zlatko

[minux]

On Fri, Dec 2, 2016 at 4:58 AM, Zlatko Čalušić <zcal...@bitsync.net> wrote:

Hello,

and thanks for another great Go release!

I have just one question, and it's not specific to this beta, but all Go betas and rc-s.

I compile Go from repository like this:

cd $HOME/src/go.googlesource.com/go
git checkout -f master
git clean -fdx
git pull --ff-only
git checkout -f go1.8beta1
cd src && make.bash

The resulting binary unfortunately is not labeled as go1.8beta1, but instead:

go version devel +41908a5 Thu Dec 1 02:54:21 2016 +0000 linux/amd64

What follows next is that various Go software, where developers decided to explicitely test for Go version (and of course don't deal well with devel versions) fails to compile. One example is gopherjs, it's uncompilable with this beta version, unless I manually edit the source and remove gratuitous checks.

The question is, how do I persuade the compiled beta to report version as go1.8beta1?

Because betas are just tags from the master branch, there is no way to change the

VERSION file to read go1.8beta1. If you're going to report an issue, just include the

full "go version" and it should be fine. If you insist on having go version report go1.8beta1,

you can create a VERSION file at $GOROOT that read "go1.8beta1" and rebuild Go.

However this is not recommended as git repository is a moving target and if you

checkout a new revision without removing the VERSION file, the reported version

would still be go1.8beta1, which will be really confusing.

However, if you download the go1.8beta1 source tarball, then the VERSION file will

correctly indicate go1.8beta1.

[Zlatko Čalušić]

Ah, I see... Thank you for the hint minux!

I can live with a bit of manual editing, it's not that beta's are released every day. :)

Also git clean -fdx step from my simple compilation script takes care of removing stale VERSION files, so all should be OK.

go version go1.8beta1 linux/amd64

Yay! :)

Now, to see if gopherjs fancies THIS version string...

-- 
Zlatko

[ma...@influxdb.com]

The last sentence under the Compiler Toolchain heading:

> Compared to the previous release, Go 1.8 is about 15% faster.

This would be a little more clear if it said something more like "Compared to the previous release, running go build in Go 1.8 is about 15% faster."