Skip to content

Conversation

@paulvollmer
Copy link

No description provided.

Copy link
Member

@KjellMorgenstern KjellMorgenstern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd advise to limit the number of supported versions. Although it seems to be pretty stable, it might prove a lot of work to keep all that versions working at all time.

Also, 'tip' might be changing any time. I think it should be our decision when to switch to a new version of go, and not let it to random (or whatever travis decides).

So, I'd suggest to decide for two or three versions, that we can support for the next years, eg. 1.10 and 1.12 .

@paulvollmer
Copy link
Author

i think we do not get problems with new releases until go 2 and the planned changes at the error and fmt packages.

but yes, i think it's less work for us to only test the latest few versions...

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants