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

upper bound on SDK constraint is not good practice #38

Closed
jmesserly opened this issue Oct 8, 2013 · 0 comments
Closed

upper bound on SDK constraint is not good practice #38

jmesserly opened this issue Oct 8, 2013 · 0 comments
Assignees

Comments

@jmesserly
Copy link
Contributor

Since the SDK cannot be downgraded, it is not generally a good practice to put a cap on it. When we asked for SDK constraints we promised never to put an upper bound :)

Concretely, this caused a problem for me because I couldn't use/test quiver on 0.8.x, even though in fact the feature I wanted to use worked just fine.

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

3 participants