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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

`0.x.x` versions have confusing and not widely known semantics #314

Closed
matthew-andrews opened this Issue Feb 11, 2015 · 4 comments

Comments

Projects
None yet
4 participants
@matthew-andrews
Member

matthew-andrews commented Feb 11, 2015

0.x.x versions have confusing and not widely known semantics (minor => major, patch => minor, patch => 馃挩).

My feeling is that we should ban them and always start from 1.0.0.

@quarterto

This comment has been minimized.

Show comment
Hide comment
@quarterto

quarterto Feb 11, 2015

Member

FWIW npm init changed the default package.json version to 1.0.0 a few months back.

Member

quarterto commented Feb 11, 2015

FWIW npm init changed the default package.json version to 1.0.0 a few months back.

@matthew-andrews

This comment has been minimized.

Show comment
Hide comment
@matthew-andrews

matthew-andrews Feb 11, 2015

Member

@quarterto nice I didn't know that! (my npm init is echo {} > package.json)

Member

matthew-andrews commented Feb 11, 2015

@quarterto nice I didn't know that! (my npm init is echo {} > package.json)

@kaelig

This comment has been minimized.

Show comment
Hide comment
@kaelig

kaelig Feb 16, 2015

Contributor

As decided in last meeting, we'll experiment with going for 1.0.0 versions. Authors can now use beta versions + experimental flags when needed.

Contributor

kaelig commented Feb 16, 2015

As decided in last meeting, we'll experiment with going for 1.0.0 versions. Authors can now use beta versions + experimental flags when needed.

@triblondon triblondon self-assigned this Feb 16, 2015

@triblondon

This comment has been minimized.

Show comment
Hide comment
@triblondon

triblondon Feb 16, 2015

Contributor

Yes, me to update spec

Contributor

triblondon commented Feb 16, 2015

Yes, me to update spec

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