Proposal to follow semantic versioning for Infusion

[Justin Obara]

Currently Infusion is using a 4 component (number) versioning system. Full details can be seen on the Fluid Versioning Scheme wiki page. While updating the version of Infusion from 1.5 (just tagged) to the in development 2.0 as part of FLUID-5449, we hit a bug in the package.json file where a version of 2.0-SNAPSHOT would cause an error in npm. The reason for this is that it does not pass the semver validator. The fix was simple, 2.0.0-SNAPSHOT; however it indicates that we've already implicitly moved to supporting Semantic Versioning.

The difference between our current versioning scheme and Semantic Versioning is fairly minor. Apart from being much more defined, it has one fewer components, but does support patch and build specific versioning. 

I propose we just make the move to following the Semantic Versioning standard.

Thanks
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20140619/9935009c/attachment.html>