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

Jump to bottom

doc: update the contribution guidelines to reflect the new minor release process #25018

Closed
FiloSottile opened this issue Apr 23, 2018 · 1 comment
Closed

doc: update the contribution guidelines to reflect the new minor release process #25018

FiloSottile opened this issue Apr 23, 2018 · 1 comment
Labels
Documentation FrozenDueToAge
Milestone
Go1.10.3

Comments

@FiloSottile
Copy link
Contributor

From https://golang.org/doc/contribute.html#master:

Most Go installations use a release branch, but new changes should only be made based on the master branch. (They may be applied later to a release branch as part of the release process, but most contributors won't do this themselves.)

This is out of date in respect to https://github.com/golang/go/wiki/MinorReleases.
@FiloSottile FiloSottile modified the milestones: Go1.11, Go1.10.2 Apr 23, 2018
@andybons andybons modified the milestones: Go1.10.2, Go1.10.3 Apr 30, 2018
@FiloSottile
Copy link
Contributor Author

This was fixed by a3d8326, and I'm not inclined to add a section about cherry picks. There's no need to overload contributors with information they'll not need most of the times. gopherbot links to the wiki when backport issues are probably enough.

@golang golang locked and limited conversation to collaborators May 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Documentation FrozenDueToAge
Projects
None yet
Milestone
Go1.10.3
Development

No branches or pull requests
3 participants
@andybons @FiloSottile @gopherbot