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

What's needed for 1.0? #215

Open
mike-north opened this issue Aug 27, 2018 · 2 comments
Open

What's needed for 1.0? #215

mike-north opened this issue Aug 27, 2018 · 2 comments
Labels

Comments

@mike-north
Copy link

If this library aims to follow SemVer, the current version number indicates that the API should not be considered stable

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

I suspect that the current API is in fact stable. Can we call this 1.0?

@Turbo87
Copy link
Member

Turbo87 commented Aug 27, 2018

It is sort of stable, but since we're still using an old mocha version I wouldn't want to call it 1.0 until we're using the latest

@a13o
Copy link

a13o commented Sep 9, 2018

I think v1.0 should drop support for the two older styles of test helpers (describeComponent, setupComponentTest, etc) now that Ember has unified testing. That will make this project a lot easier to maintain.

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

No branches or pull requests

3 participants