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

Get 1.0.0 out #404

Open
paulmillr opened this issue Jan 31, 2016 · 4 comments
Open

Get 1.0.0 out #404

paulmillr opened this issue Jan 31, 2016 · 4 comments

Comments

@paulmillr
Copy link
Owner

Thoughts on this? We almost have ES2016 at this point.
@ljharb
Copy link
Collaborator

ljharb commented Jan 31, 2016

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.

@JSteunou JSteunou mentioned this issue Feb 9, 2016
Closed
@sonicoder86
Copy link

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.

@ljharb
Copy link
Collaborator

ljharb commented Mar 3, 2016

@BlackSonic it should still work fine if using ^, which for < 1.0 releases upgrades the patch version (which is the only nonbreaking thing that can be updated pre-1.0)

@sonicoder86
Copy link

Yes i just realized that minor version changes pre-1.0 are actualling breaking changes

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

No branches or pull requests
3 participants
@ljharb @paulmillr @sonicoder86