Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Versioning #85

Closed
AidasK opened this issue Aug 7, 2013 · 1 comment
Closed

Versioning #85

AidasK opened this issue Aug 7, 2013 · 1 comment

Comments

@AidasK
Copy link
Contributor

AidasK commented Aug 7, 2013

Hi,

i think this library is getting bigger and lots of breaking changes were made recently.
I suggest to tag current version as v0.1.0.
Create develop branch.
And then we are finished with all the issues, we could tag it as v1.0.0.

This will be a big help for people who are using package managers such as bower.

@steffentchr
Copy link
Member

Let's call this 1.0. And work on a 2.0, since the scope would be breaking changes.

We will tag up the repository and do this after having gone through the outstanding issue list for this version. Will also be adding in:

this.version = 1.0;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants