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

Stack fails to build for LTS-6.15 and LTS-6.16 on Windows due to Yaml library #1854

Closed
azverkan opened this issue Sep 8, 2016 · 8 comments
Closed

Comments

@azverkan
Copy link

azverkan commented Sep 8, 2016

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?

@DanBurton
Copy link
Contributor

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.

@azverkan
Copy link
Author

azverkan commented Sep 8, 2016

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.

@juhp
Copy link
Contributor

juhp commented Sep 9, 2016

Well the problem is we only build stackage for Linux...

@DanBurton
Copy link
Contributor

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 6.X, you should be able to upgrade safely to a later version in the LTS 6 series.

@juhp
Copy link
Contributor

juhp commented Sep 9, 2016

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...

@juhp
Copy link
Contributor

juhp commented Sep 9, 2016

(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... :-)

@azverkan
Copy link
Author

azverkan commented Sep 9, 2016

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 :)

@snoyberg
Copy link
Contributor

LTS-6.17 is now out with an upgraded yaml version.

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

No branches or pull requests

4 participants