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.

Sign up for GitHub

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

Define and implement Go version policy #434

Open

MichaelRybak opened this issue Jun 8, 2020 · 0 comments

Assignees

Labels

fixit

Contributor

MichaelRybak commented Jun 8, 2020

Let’s establish a policy that determines the versions of Go amppackager is compatible with. Specifically:

Which major releases: all of Go 1.10+, or some of them?
Which minor releases: all of Go 1.10+.*, or some of them?
When is the policy updated?

The policy must be reflected by the project’s processes and documentation:

Travis must check against all compatible Go versions.
Manual setup procedure in README.md should mention supported versions and capture the differences between the setup procedures - e.g. the need for “-mod=vendor” flag.
Contributing Guidelines should mention the policy and how it’s enforced by Travis.
Document the policy

MichaelRybak self-assigned this

MichaelRybak added the fixit label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment