Understanding what goes into each release/tag

[ericf]

I've opened several issues requesting a changelog so I can understand what goes into each release of Handlebars, but we're not there yet.

I understand that the npm tags are different from the main release tags, but I cannot reason about what code I'm running.

1.0.0-rc.3 != v1.0.9: https://github.com/wycats/handlebars.js/compare/1.0.0-rc.3...v1.0.9?w=1

1.0.0-rc.3 != v1.0.10: https://github.com/wycats/handlebars.js/compare/1.0.0-rc.3...v1.0.10?w=1

1.0.0-rc.3 -> v1.0.9 -> v1.0.10 represents a large number of changes, all of which appear to be under RC-3. This tagging inconsistency combined with a lack of a changelog makes it very hard to keep up with the changes of this project.

Could you please make the following changes:

• Add a changelog (pretty please!)
• Use consistent tagging between releases and npm packages. (Or at least create two tags every time a new version is published somewhere.)

Thanks!

[caridy]

👍

[tivac]

👍 from me as well. Trying to track Handlebars versions is crazy-making.

[kpdecker]

We are going to unify the versioning once we get up to 1.0 client out the door. There are a variety of factors mostly revolving around node's semver implementation that forced us to separate the version numbers.

[ericf]

@kpdecker Yeah I understand that. But I would still like to see Handlebars.VERSION bumped when the npm package is published (and tagged with its own scheme) and the website updated with the new version number, along with a changelog for that release.

[kpdecker]

Release notes added. For future releases we will sync up the node vs. browser packages.

[ericf]

Thanks! ❤️