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

Pessimize generates overly restrictive requirements #8

Open
drbrain opened this issue Aug 15, 2013 · 3 comments
Open

Pessimize generates overly restrictive requirements #8

drbrain opened this issue Aug 15, 2013 · 3 comments
Assignees
Milestone

Comments

@drbrain
Copy link

drbrain commented Aug 15, 2013

Correct specification for semantic versioning is described in the RubyGems guides patterns for declaring dependencies. You lock users to a bug fix series and don't allow backward-compatible releases with new features.

For >= 1.2.3 the semantic-versioning-safe requirement is ~> 1.2, >= 1.2.3.

@drbrain
Copy link
Author

drbrain commented Aug 15, 2013

I've added an example to the rubygems guides rubygems/guides@ef777b4c

@joonty
Copy link
Owner

joonty commented Aug 16, 2013

Thanks for this, I completely agree.

I originally locked it to patch level upgrades because I had a project where a supposedly minor upgrade was not in fact backwards compatible. But it shouldn't be the default any more.

I'm planning on adding options to the command line script, which will give the user the choice of how restrictive/permissive they are with their version upgrades.

Thanks again

@joonty joonty added this to the Version 0.4.0 milestone Nov 11, 2015
@joonty joonty self-assigned this Nov 11, 2015
@joonty
Copy link
Owner

joonty commented Nov 11, 2015

I'm finally going to tackle this one for the next version release. I'll post updates here.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants