New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all: Go 1.15beta1 release status #39502
Labels
Comments
Log
|
Latest build: go1.15beta1
Log
|
We are investigating a possible issue in the release, and will not be moving forward with it today. We'll check in tomorrow after some more investigation. |
We're moving forward with the beta1 release today. We've discovered at least #39533 as an issue to investigate. |
Change https://golang.org/cl/238539 mentions this issue: |
gopherbot
pushed a commit
to golang/build
that referenced
this issue
Jun 18, 2020
The windows-amd64-longtest target is passing on master (for Go 1.15), release-branch.go1.14, and release-branch.go1.13. It was successfully opted-into during the Go 1.15 Beta 1 release (see golang/go#39502). Start including it in the release process by default, so that we have more information available during the upcoming releases, and in turn can use it to improve the releases and the release process further. Also improve the formatting of the release table to improve its readability, based on experience from golang/go#39502. For golang/go#29252. Change-Id: I002c3bf811facf50ca5fb363adebe2baacd039ea Reviewed-on: https://go-review.googlesource.com/c/build/+/238539 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue tracking the go1.15beta1 release by releasebot.
The text was updated successfully, but these errors were encountered: