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

Publish #232

Closed
dcousens opened this issue Jun 3, 2015 · 6 comments
Closed

Publish #232

dcousens opened this issue Jun 3, 2015 · 6 comments
Assignees
Milestone

Comments

@dcousens dcousens added this to the 0.5.0 milestone Jun 3, 2015
@dcousens
Copy link
Collaborator Author

dcousens commented Jun 5, 2015

Please wait on #197 to be merged before publish.

@iam4x
Copy link
Contributor

iam4x commented Jun 8, 2015

I think that a minor should change the last digit, so go for 0.4.10 ?

@brianreavis
Copy link
Collaborator

If we're following semver, 0.5.0 is the way to go.

Given a version number MAJOR.MINOR.PATCH, increment the:
"MINOR version when you add functionality in a backwards-compatible manner"

@iam4x
Copy link
Contributor

iam4x commented Jun 8, 2015

@brianreavis Thank's for the information 👍

@JedWatson
Copy link
Owner

I'm going to release anyway despite #197 not being ready. There's too many other improvements and fixes that I want to publish. Let's try and wrap onAdd/onCreate etc soon and it can be published in a subsequent version. I don't think it's going to cause an issue for anyone if we release without that for now.

@JedWatson
Copy link
Owner

0.5.0 is in the wild, going to close this now.

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

4 participants