Policy on bumping the version number

[jordanbtucker]

At the time of this writing, this project's version number is 0.4.0 and hasn't been updated since Nov 2014. Let's discuss a policy on when and how version numbers should be updated.

SemVer is probably the best fit for this project. If we adopt SemVer, we should define when 1.0.0 is ready to be released, since anything with a major version 0 really has no meaning in SemVer.

[aseemk]

I'd be okay with just considering the current spec/code 1.0. The main missing feature from the implementation is proper Unicode support, but that's a code issue, and the spec probably matters more than the code (since the code is just a reference implementation).

👍 to semver in general.

[jordanbtucker]

I think I might make this v0.5.0. I'd like to get the following PRs merged before v1.0.0:

• Move isWord function to its own module #89: Browserify support
  • Unquoted object keys should support non-ASCII characters #1: Unicode support
  • Add helpers file #94: helpers.js file and fix for isWord leaking into public API
• Adding a --validate CLI option #84: --validate CLI option
• Update require usage #87: slim down npm payload
• Improved ci #105: CI improvements including coveralls
• Improve command-line tool with options and streaming mode #108: streaming command line and yargs runtime dependency

Once we implement Browserify, we should be able to add in Unicode support.

[jordanbtucker]

@aseemk
v0.5.0 is released, but I don't have permission to publish to npm. Thanks.

[aseemk]

@jordanbtucker: Your suggestion SGTM. I'll also give you npm publish access! Thanks again for all your great work — it's really helpful to have your hands here.

[aseemk]

Looks like I need to know your npm username?

[aseemk]

Ah, jordanbtucker naturally. =) Added!