Nice thanks for sharing that :)
On 27/01/2017 16:42, [email protected] wrote:
A better link is this one, IMHO:
github.com/golang/go/compare/go1.7.4...go1.7.5
the gerrit one shows uninteresting CLs too, like:
[release-branch.go1.7] cmd/godoc: add perf subrepo
while the github one doesn't
Il giorno venerdì 27 gennaio 2017 15:58:20 UTC+1, Steven Hartland ha
scritto:
Hi guys first off thanks for 1.7.5!
Having reviewed the changes for the 1.7.5 milestone
<https://github.com/golang/go/issues?q=milestone%3AGo1.7.5>, which
is the link provided for more info from the release notes, I feel
that the its not as easy to follow as they have been for other
milestones, which means that users may not realise the impact as
well as they should.
The data is there but you really have do dig in to see it, I'm
referring specifically to the "backport" changes:
* time, cmd/compile: backport fixes to 1.7.5
* runtime: backport CL 34835
* runtime: backport CLs 33339 and 35353
* runtime: backport CL 31138
In the past each fix has been in the original format which would
have resulted in something like:
* time: TestLoadFixed failure
* cmd/compile: passing method on value receiver causes memory
corruption
* runtime: fatal error: bad g->status in ready
* runtime: fatal error: scan missed a g
* runtime: fatal error: unexpected signal during runtime execution
* runtime: getArgInfo nil dereference
Its important to know that these are issues that "were actually
raised" and are fixed by changes in the release, it is NOT the
list of fixes which users are likely expecting.
Its good to know the "issues" which have been closed by the
release, but its more useful to know all the "changes" in the release.
This is something that jenkins can do:
https://go-review.googlesource.com/#/q/status:merged+branch:release-branch.go1.7++after:2016-12-02+before:2017-01-27
<https://go-review.googlesource.com/#/q/status:merged+branch:release-branch.go1.7++after:2016-12-02+before:2017-01-27>
Is this something we can include for releases moving forward?
On 26/01/2017 21:19, Chris Broadfoot wrote:
Hello gophers,
We have just released go1.7.5, which includes fixes to the compiler,
runtime, and the crypto/x509 and time packages.
https://golang.org/doc/devel/release.html#go1.7.minor
<https://golang.org/doc/devel/release.html#go1.7.minor>
You can download binary and source distributions from the Go web
site:
https://golang.org/dl/
We also released go1.8rc3, a release candidate of Go 1.8.
It is cut from release-branch.go1.8 at the revision tagged go1.8rc3.
Thank you to everyone who has helped to test Go 1.8 so far.
Your help is invaluable.
Report any problems using the issue tracker:
https://golang.org/issue/new
If you have Go installed already, the easiest way to try go1.8rc3
is by using this tool:
https://godoc.org/golang.org/x/build/version/go1.8rc3
<https://godoc.org/golang.org/x/build/version/go1.8rc3>
You can download binary and source distributions from the usual
place:
https://golang.org/dl/#go1.8rc3 <https://golang.org/dl/#go1.8rc3>
To find out what has changed in Go 1.8, read the draft release notes:
https://beta.golang.org/doc/go1.8 <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
--
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 [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
