Versioning scheme doesn't work well with npm

maxtaco / coffee-script

IcedCoffeeScript

http://maxtaco.github.com/coffee-script

MIT License

727 stars 58 forks source link

Versioning scheme doesn't work well with npm #136

Open s4y opened 9 years ago

s4y commented 9 years ago

The current version is 1.8.0-a, which semver treats as a prerelease. This means that I can't add a dependency to my project like ~1.8. Would you consider dropping the -letter suffix from release versions?

maxtaco commented 9 years ago

The system is set up like it is so I can issue several releases for each release Jeremy issues in the main CoffeeScript. Is there an alternate versioning system I could use to achieve this?

I guess I could do something like:

ICS v1008.0.0 -> CS1.8.0, ICS release 0 ICS v1008.0.1 -> CS1.8.0, ICS Release 1 ICS v1008.1.4 -> CS1.8.4, ICS release 4

It's a big ugly though

s4y commented 9 years ago

Oof, I didn't realize that. The only other option I can think of is to fork ICS's version from CS and use a + to add the CS version as "build metadata" (which semver ignores). Some examples:

v1.8.0+CS1.8.0 (start with the current version)
v1.8.1+CS1.8.0 (ICS bug fix, same CS)
v1.8.2+CS1.8.4 (merge CS bug fixes)
v1.9.0+CS1.8.4 (new ICS feature, same CS)
v1.10.0+CS1.9.0 (merge new CS feature)