go 1.0 + comply with semver

[Raynos]

semver says

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

This means that 0.9.1 could break back compat of async, which is very sad.

async seems to be a rock solid production quality piece of software.

It's ready to go 1.0 and comply with semver, i.e. all new additions to the interface bump minor, and any breaking changes to the interface will bump major.

[rlidwka]

1.0.1 can break b/w compat with 1.0.0 as easy as 0.9.1 can break it with 0.9.0. There is no practical difference.

[aearly]

@rlidwka Of course it can, but if semver best practices are followed, a patch release should not introduce new bugs or features. The way to guard against regressions is a large corpus of tests, which async has. If you add a feature, make it a minor release.

The main reason behind a 1.0 release would be to signify that the API and list of features is stable, and ready for production use. Given async's popularity, and 11-month hiatus in updates last year, I'd say it's already there de facto. There's a couple open issues that would be nice to have (like forEachOf) for a a 1.0 release though.

[rlidwka]

Of course it can, but if semver best practices are followed, a patch release should not introduce new bugs or features.

Yes, except most node.js libraries don't follow semver. They follow these semantics:

revisions = no b/c breaks
minors = b/c breaks for some
majors = b/c breaks for everyone

Async library fits here, as far as I know.

[Raynos]

most node.js libraries don't follow semver.

That's a bad thing (tm).

Hence this issue is about asking the author to comply with semver for any future facing changes. There are no disadvantages to complying with semver.

[rlidwka]

There are no disadvantages to complying with semver.

Strict semver compliance would require major version bump every second release. If you switch null to undefined, 99% of people won't even notice, but you have to increase first digit. I'm pretty sure that's a bad thing (unless you really enjoy waiting a year for an official release).

[Raynos]

Yeah that's fine. just bump the major version number.

There's nothing wrong with bumping the major version number 5 times on one day. That's deprecating 5 bad features, congratulations.

[aearly]

Also, one of the provisos of semver is before a 1.0 release, minor revs could be considered the equivalent of major revs, since it's considered "unstable". After 1.0 we'd have to be more strict.

[aearly]

Version 1.0.0 published!