Skip to content
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: switch to Go 1.15 as default inside Google #39691

Open
dmitshur opened this issue Jun 18, 2020 · 3 comments
Open

all: switch to Go 1.15 as default inside Google #39691

dmitshur opened this issue Jun 18, 2020 · 3 comments

Comments

@dmitshur
Copy link
Member

@dmitshur dmitshur commented Jun 18, 2020

This is the tracking bug for switching to Go 1.15 inside Google.

When all internal release-blocking bugs & serious performance regressions are fixed and the default is flipped, then this can be closed.

This is a release-blocker for go1.15rc1, per our normal release policy (a precondition for public rc1 == Google's using it themselves already).

Previously #36717.

/cc @golang/osp-team @neild @bradfitz

@dmitshur dmitshur added this to the Go1.15 milestone Jun 18, 2020
@elfgoh
Copy link

@elfgoh elfgoh commented Jul 1, 2020

As a curiosity, is there a link that I can read more to understand the reason behind this condition in the release policy? The only other issue I could find was #36717. So maybe I am not looking in the right place

@dmitshur
Copy link
Member Author

@dmitshur dmitshur commented Jul 1, 2020

@elfgoh There’s some additional motivation described on the Go Release Cycle page:

One of the criteria for issuing a release candidate is that Google be using that version of the code for new production builds by default: if we at Google are not willing to run it for production use, we shouldn't be asking others to.

I recommend reading that entire page as it provides context for each milestone and the process leading up to the final release.

@elfgoh
Copy link

@elfgoh elfgoh commented Jul 1, 2020

if we at Google are not willing to run it for production use, we shouldn't be asking others to.

Thanks @dmitshur . I was guessing the above, but wanted to be sure 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.