Go policy does not fully support previous release

[Liam]

I was startled to learn that regressions found in the previous release (currently 1.12.x) will not be fixed in that release. Regressions are only fixed in the most recent release.

If you wait until 1.12.5 to upgrade a deployment from 1.11.x, and then discover a regression on the day 1.13 comes out, tough luck. Either upgrade again to 1.13 or resort to a custom build.

I filed a proposal to change this:

https://github.com/golang/go/issues/34622

[Christoph Berger]

A question based on genuine interest: Which factors make it hard for you to upgrade to the latest Go release?

[Axel Wagner]

Hey,

just because you asked for community-input multiple times (and I don't want to see claims again, that the Go team would ignore community input): I was aware of this policy and I agree with it.

If nothing else, consider that as *users* of Go, we also benefit from this policy. Because at the end of the day, you also have to decide how many Go versions back you want to support for your software. The fact that there is no LTS-version of Go or whatever and that you can pretty much assume "the current version and maybe the last" to be stable, simplifies things for the ecosystem at large.

Also, your arguments can just as well be made about the previous to last version, or the one before that, or the one before that… ad infinitum. Clearly it's unreasonable to expect changes to be backported to *all* releases, so some cutoff has to be decided. Which is, all things considered, still arbitrary. 

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9964ea39-6978-4fb0-83bb-bd7cbd509ee7%40googlegroups.com.