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

Decide requirements for 1.0.0 release #2

Open
MattMS opened this issue Nov 19, 2014 · 1 comment
Open

Decide requirements for 1.0.0 release #2

MattMS opened this issue Nov 19, 2014 · 1 comment
Assignees
@MattMS
Labels
help wanted question

Comments

@MattMS
Copy link
Owner

MattMS commented Nov 19, 2014

While in 0.x.x, I am still trying to follow the semver rules but I don't want this to cruise in 0-land forever.
@MattMS MattMS self-assigned this Nov 19, 2014
@MattMS
Copy link
Owner Author

MattMS commented Nov 19, 2014

From semver FAQ:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MattMS MattMS

Labels
help wanted question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MattMS