Version matching

[michaek]

Is the project still matching tags to Compass versions, per #1? It seems like it's not, because there's no Compass 1.0.2. Should there be a different versioning pattern that will reflect the Compass version, and our patch level appended to the end? Semantic Versioning's pre-release section would permit something like 1.0.1-0.0.2. Ideally we wouldn't need a second major version, because we shouldn't be breaking backward compatibility if Compass isn't, but I suppose it could happen...

Is our goal to only match the most current version of Compass, or to provide compatibility back to the 0.12.x minor version?

[Igosuki]

Yeah, actually mismatched versions only provoke warnings. What I wanted was to push fixes with new tags and let people figure out which version of Compass the tag is bound to from the doc or the json configuration files, but that's clearly problematic.
We can rename all 1.0.x+ tags as 0.12.3-0.0.x.
As for compass versions, we can simply incorporate changes and bump the major/minor to the same number. Of course we then keep using pre-release semantics for old releases critical bug fixes or compatibility with newer SASS features if such pull requests arise.

[michaek]

This makes sense to me. Thanks!