-
Notifications
You must be signed in to change notification settings - Fork 388
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
Get 1.0.0 out #404
Comments
I'd hoped to make it more modular first so that v1.0.0 would collect a bunch of breaking changes at once, but that's OK to do in a v2.0.0. I would like to drop bower and component support as part of v1 at least, as well as start with a fixed tagging scheme. |
It would be good, because on projects like Angular 2 that allow minor version upgrades it can be upgraded. Now it is not possible because of pre 1.0 version. |
@BlackSonic it should still work fine if using |
Yes i just realized that minor version changes pre-1.0 are actualling breaking changes |
Thoughts on this? We almost have ES2016 at this point.
The text was updated successfully, but these errors were encountered: