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.

Sign up for GitHub

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

Jump to bottom

versioning and NPM publish #61

Open
millermedeiros opened this issue Aug 7, 2012 · 2 comments
Open

versioning and NPM publish #61

millermedeiros opened this issue Aug 7, 2012 · 2 comments
Labels
enhancement task

Comments

@millermedeiros
Copy link
Owner

Maybe we should do releases every month or so (or when we group a couple new features) and do point releases for bug fixes.
@millermedeiros
Copy link
Owner Author

until now each method has it's own version number and update date. API and packages are very stable for the past 10 months but using a version number for the whole package will make it easier to update it in the future (specially if it is a breaking change). I think we should remove version numbers from each method to avoid confusions.

@millermedeiros
Copy link
Owner Author

maybe create a pre-commit hook that grabs the version number from package.json and update the component.json and add a VERSION property to the index.js as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@millermedeiros