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

Strip leading v from versions before we compare them. #121

Merged
merged 1 commit into from Mar 26, 2015
Merged

Conversation

ralphbean
Copy link
Contributor

Kinda fixes #110.

@pypingou
Copy link
Member

I didn't really want to go this road because I thought we could use this to teach upstreams to be consistent in their release naming, but ok 👍

@ralphbean
Copy link
Contributor Author

teach upstreams to be consistent in their release naming

But projects which have already switched format cannot rewrite their release history. Ansible, for instance, already has github tags in two different formats and I don't think we can argue that they should go back and rename the old ones.

Plus, teaching all upstreams something is probably a sisyphean task. 😉

ralphbean added a commit that referenced this pull request Mar 26, 2015
Strip leading v from versions before we compare them.
@ralphbean ralphbean merged commit e7ca268 into master Mar 26, 2015
@ralphbean ralphbean deleted the leading-v branch March 26, 2015 13:56
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

Successfully merging this pull request may close these issues.

Problems when the version numbering format changes
2 participants