Back

@www.jvt.me yeah, that really doesn’t make any sense to me. If you push the first version of anything as 1.0, your users will have no idea that they should expect breaking changes on pretty much a daily basis.

1.0 to me means “we’re happy with our API” and getting to that point with any project is normally something that requires not just time, but *actual users*. Doesn’t mean it can’t ever change, but that there’s going to be a lot of thought behind future (breaking) changes.

go-semantic-release has this same default but thankfully it's straightforward to set it so you can use 0.x releases.

Making it the default is IMO a very bad decision, as it teaches people that they should go to 1.x far too early.

My grumbling will result in a blog post sooner than later

Et voila

@www.jvt.me An excellent blog! And one I'll use as reference whenever this comes up. Even had me go back an correct a typo in one of my posts you linked, lol

Thanks! Wondering if it'll get more traction on Hacker News or whether it's maybe a bit wordy

@www.jvt.me Just woke up after a 4 hour nap at home where I'm fighting the cold from hell, but I saw it now and upvoted :)

Oh no, feel better