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

STOP breaking backwards-compatibility with patch versions #551

Closed
paulmillr opened this issue Jun 4, 2013 · 1 comment
Closed

STOP breaking backwards-compatibility with patch versions #551

paulmillr opened this issue Jun 4, 2013 · 1 comment

Comments

@paulmillr
Copy link

Seriously, folks.

1.0.10 compiles stuff in one way and 1.0.12 compiles it in totally different way.

Please stop breaking compat with patch versions. Breaking it with 1.0 -> 1.1 is totally fine.

lots of users depend on proper semantic versioning. gh-547, brunch/brunch-with-chaplin#75, http://ost.io/@brunch/brunch/topics/89 etc

@kpdecker
Copy link
Collaborator

kpdecker commented Jun 4, 2013

We had semver issues that forced us to do patch versions. The next version will be 1.1.0-alpha.01. We have had discussions and the goal is to not break the runtime and precompiler API until we hit 2.0, whatever that may look like.

That being said I strongly suggest running your runtime and precompiler in lock step as this is what is tested by our test suite, not permutations of 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

No branches or pull requests

2 participants