-
Notifications
You must be signed in to change notification settings - Fork 797
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
Stack fails to build for LTS-6.15 and LTS-6.16 on Windows due to Yaml library #1854
Comments
We usually treat images as immutable, and address such issues by releasing a new image in the series. (e.g. LTS 6.17) Perhaps we should also maintain an image blacklist for those with known issues. |
That's what I was expecting. It is just that the nomenclature of calling it a "Long Term Support" release is a bit weird if it is not actually supported. |
Well the problem is we only build stackage for Linux... |
The "support" comes not from supporting a specific point release (e.g. 6.16), but rather by having subsequent releases that are backwards compatible. The idea is that if you have a trouble with |
And 6.16 was rolled early specifically to address snoyberg/yaml#94 :) It would be nice if someone could confirm the next yaml release works on Windows before we roll 6.17... |
(FWIW personally I don't think the name "LTS" makes so much sense either, but it has kind of stuck now - and I don't have a better name... :-) |
The word "release" has been used in this context for quite a while now and the typical short version "rel" I have seen in use for various projects going back at least 20 years :) |
LTS-6.17 is now out with an upgraded yaml version. |
6.15 fails to build with this issue:
snoyberg/yaml#94
6.16 dies with this issue:
snoyberg/yaml#96
Is policy for LTS to fix regressions in older releases? Or should those releases just be blacklisted for Windows clients?
The text was updated successfully, but these errors were encountered: