Create a dev branch for development and keep master at current release version on npm

[thethomaseffect]

I'm one of the new maintainers assigned to this project. I propose we introduce a dev branch so that it's easier to iterate and ensure master is always deployable to npm. This lets us test new features and changes for a while before incrementing package.json's semantic versioning (As well as making it easier to maintain a changelog).

This would also allow us to start updating and merging old pull requests such as #35 without waiting on the original authors to come back. That way we can make a lot of progress towards reaching 0 issues and pull requests (Since people get discouraged to write a fix if they see a lot of existing pull requests, thinking it wouldn't get merged).

What are other peoples take on this?

[SomeKittens]

Hey! Glad to see you. As to the dev branch, I don't think it's entirely needed. Most projects have master as cutting edge and include tags to npm deployments.

[rlidwka]

Bad idea, people usually make pull requests against master branch, and another dev branch would be confusing.

If you want to have a stable / always deployable branch, just create a separate one for that.

[thethomaseffect]

Cool, will stick with just master, thanks for the input guys!