Release 1.0 about croniter HOT 11 CLOSED

Sorry wasn't trying to push for a 1.0 release, but I do appreciate it regardless, thanks! (only stumbled across this as I've been using it for a few years and was curious about 1.x)

from croniter.

My apologies if my comment came along as abusive.

My intent was purely to sincerly thank you for cutting a release.

In addition I wanted to express that it's more convenient for external dependencies to have major version > 0 IF developers/projects are used to reason about API stability in terms of semver.

So thank you again for making croniter available and cutting this release and sorry that this wasn't clear from the wording of my comment.

from croniter.

interface is stable for years, nothing has drastically changed at the point to change to a new major version.

from croniter.

For now croniter does not added any invasive change that introduced api breakage.

We may change the minor in the next release as we will introduce some new code to handle better DST transition, but the major will not change, for 1.

from croniter.

That's a bit unfortunate as the semver guidelines also state that 0.x.y versions indicate it has an unstable API. They say if it's stable or used in production it should ideally be released as 1.x.y

I wonder if it's worth stating this in the readme so people know the API is stable even though it's 0.x

from croniter.

Please see changelog, croniter is 11 years old.

It would have been known if it would not be stable.

from croniter.

btw, i will just make another commit release for making you happy ;)

from croniter.

1.0.1 released.

from croniter.

no problem, if you felt there was something todo, there was certainly something todo.

from croniter.

Thanks for releasing 1.0.1! This will further increase the usefulness for projects which rely on semver guidelines to reason about API stability (thanks to @MisguidedEmails for linking to the relevant specifications).

from croniter.

Sorry, but i can't let you say that @trendelkampschroer, it's truely abusive.

It's only for semver where a 0.X release implies it's on a development state.

croniter was for now NOT USING SEMVER but regular library versioning so you can't access that, SORRY.

a good exemple would be https://en.wikipedia.org/wiki/OpenSSL which turned 1.0 long time after initial stable release ;-)

from croniter.