Go 1.15 release status

[Dmitri Shuralyov]

Hi gophers,

It's been almost two weeks since we released Go 1.15 Beta 1. Thanks to everyone who has helped test it, reported bugs, and made progress toward the final release.

Today, we have 15 open issues with the release-blocker label in the 1.15 milestone. With the exception of “all: write release blog post” and “all: refresh CONTRIBUTORS file before release” issues, these are blocking issues for Go 1.15 RC1.

The target date for RC1 is July 1, which is next week. We’ll be able to release RC1 as soon as all release blockers (other than those 2 which are safe to do anytime before final release) are resolved and we have high confidence that the tree is free of critical bugs.

If you’re assigned to an issue that is a release-blocker, please try to keep the issue updated with the latest status, and don’t hesitate to ask for help. If you're owning an issue and it doesn't have an assignee; please assign yourself so it's more visible. (Everyone is welcome to contribute to open issues, especially ones that need investigation, just be sure to communicate and coordinate your efforts.)

Thanks again for your hard work and everything you do to help make Go 1.15 an excellent release.

Thanks,

Dmitri for the release team

[Steven Hartland]

Could I suggest a few additional for consideration:

• net/http/httputil: data race in DumpRequestOut
  
• net/http/httputil: DumpRequestOut can lock up when request cancelled

And possibly this one that fixes SetConnMaxIdleTime which will be introduced by 1.15

• database/sql: idle connections are not cleaned up properly

  Regards
  Steve

--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-dev/CA%2BON-PGJ8K086r6EXLE6P4SEVV9Mw4ZNx2CYrY2qDfJbJ3YqQg%40mail.gmail.com.

[Dmitri Shuralyov]

Thanks for the suggestions Steven.

At this point in the 1.15 release freeze, we are prioritizing improving stability of the tree, fixing critical problems and regressions from 1.14, with the bar for bug fixes that is continuously raised as we get closer to the final release. Those 3 issues don't meet the criteria and need to wait until the tree reopens in August for general development and bug-fixing.

I've checked this morning, and we have 24 open issues in the Go1.15 milestone without the release-blocker label.

Please look over them, and update issues you're familiar with. They should be moved to a future milestone if 1.15 is no longer appropriate, made into a release blocker if it meets the criteria for it, or updated with a comment reflecting their current state (if there aren't already recent updates).

Thanks,

Dmitri

[dav...@gmail.com]

Hi Golang Dev Team,

are we still on track for 1.15.0? k8s is betting on this (see [1]) to get us past the EINTR issues in go1.14 for the upcoming Kubernetes 1.19 release.

Thanks,

Dims

[1] https://github.com/kubernetes/kubernetes/issues/92521#issuecomment-651261537

[Ian Lance Taylor]

On Mon, Jul 13, 2020 at 9:15 AM <dav...@gmail.com> wrote:
>
> are we still on track for 1.15.0? k8s is betting on this (see [1]) to get us past the EINTR issues in go1.14 for the upcoming Kubernetes 1.19 release.

We've been slowed down a bit by the U.S. Independence Day holiday and
by the recently announced security release. We still have a chance at
our scheduled release date of August 3, but I wouldn't be surprised if
it slips a little.

Have you been able to check whether the 1.15beta1 release fixes the problem?

Ian

[Davanum Srinivas]

Ian,

Some of our scalability jobs are at golang master tip and we've been happy with them. Thanks a ton for getting back to us. 

-- Dims

--

Davanum Srinivas :: https://twitter.com/dims