Should the next major version be v1?

[LeaVerou]

Color.js has definitely reached that level of maturity. The downside is that once you're on v1, you have to fully embrace semver, which means no backwards incompatible changes without a major version bump.

This always seemed a little too restrictive to me, often there are technically backwards incompatible changes, that only affect a tiny fraction of users, and having to bump the major version for them seems like it helps no-one.

But OTOH, it is getting a bit ridiculous to have such a mature project behind v0, and it does affect perception.

[facelessuser]

Unless there are some major areas of the code that need massive reworks, I think keeping this project on v0 doesn't make sense. I would support the idea of moving this to v1, unless some good reasons were brought to light that require adjustments before making that change, so that a plan to address them could be made.

[MysteryBlokHed]

Agreed; as long as we don't have any big reworks in mind, I'd be for doing major version 1 next

[LeaVerou]

Even if we do, that's what major versions are for!

[facelessuser]

Yep, I was more suggesting that if anyone can think of something that should block a v1 release, they should speak now. I personally can't think of anything that should block it, so I'm for a v1 release.