victorquinn/Backbone.CrossDomain

Version 0.1.0 or 0.3.0?

timolehto opened this issue · 1 comments

In Backbone.CrossDomain.js you say it's 0.1.0 but you have tagged the source tree with 0.3.0 a while ago and updated the version in the package.json numerous times. Maybe you'd like to come up with a way of keeping versioning coherent. The reason I'm asking about this is that I have a project where someone has added your Backbone.CrossDomain tweaks as a plain simple js file with nothing extra. Now it just says 0.1.0, which turns out doesn't actually give any real versioning information. So I have no idea which version of your tweaks I've stumbled upon.

Since then it has been further modified to overcome some issues with it, and now I'd like to update it to use the latest of your fixes as well and possibly contribute something back at you too. Now I basically have to diff around your repo commit by commit trying to figure out from which commit it has been created. Then I could branch out from that and apply our changes to it and then try merging it with the head of the master branch and try to resolve the conflicts.... I'm getting a headache here.. :)

@timolehto my apologies for any confusion!

In order to try and remove any further confusion, I've created another tag, 0.4.0, and updated everything across the board to that. The tag, the package.json, bower.json, and so on. This should help eliminate any confusion once and for all.