semantic versioning problem

Question

semantic versioning problem

Closed this issue 8 years ago · 5 comments

If this gem is not following semantic versioning - please ignore and close this issue.

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

http://semver.org/

So I would consider bumping version to 1.something.something (currently it is "0.10.0").

matkoniecz commented 8 years ago

Thanks!

Answer 1 · 2017-02-10T14:53:57.000Z

OK, was this auto generated comment, or a request from a human??

…

On Fri, Feb 10, 2017 at 2:58 AM, Mateusz Konieczny ***@***.*** > wrote: If this gem is not following semantic versioning - please ignore and close this issue. Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. http://semver.org/ So I would consider bumping version to 1.something.something (currently it is "0.10.0"). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#26>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAw0FekbK6Lj9dL1bCVVLgri5CZ5Bfeks5rbDTWgaJpZM4L9MlM> .

Answer 2 · 2017-02-10T15:04:20.000Z

This issue is 100% handmade by a human.

I noticed it on committing Gemfile.lock file in project that is using this gem.

Answer 3 · 2017-02-10T17:30:23.000Z

Awesome, I'll go ahead and bump it to version 1.0, my first project to even be declared that way I believe LOL. -roger-

…

On Fri, Feb 10, 2017 at 8:04 AM, Mateusz Konieczny ***@***.*** > wrote: This issue is 1000% handmade by a human. I noticed it on committing Gemfile.lock file in project that is using this gem. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAw0C-yl2CMI-Fny-WEnoY0_-1t0pW4ks5rbHx0gaJpZM4L9MlM> .

Answer 4 · 2017-02-20T16:08:12.000Z

bumped it, thanks for your contrib.

…

On Fri, Feb 10, 2017 at 10:30 AM, Roger Pack ***@***.***> wrote: Awesome, I'll go ahead and bump it to version 1.0, my first project to even be declared that way I believe LOL. -roger- On Fri, Feb 10, 2017 at 8:04 AM, Mateusz Konieczny < ***@***.***> wrote: > This issue is 1000% handmade by a human. > > I noticed it on committing Gemfile.lock file in project that is using > this gem. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#26 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAAw0C-yl2CMI-Fny-WEnoY0_-1t0pW4ks5rbHx0gaJpZM4L9MlM> > . >