I support 0ver, my open source project is currently at 0.1.9 - I'm looking forward to releasing 0.1.10 as I continue to avoid the precious 0.2 mark when I become feature complete and open the project up to a wider audience. I assume 0.3 will be a full source rewrite when I achieve Google Scale.
It's funny. With Go modules, though, there's a very real consequence of moving to 1.0.x; the build system starts imposing different constraints. Same with the move to 2.0.x. Changing versions means more than just throwing a tag in the VCS.
Most of the time, it's what you'd do anyway and isn't a bother. Sometimes - not often, but non-zero - it's an imposition.
6 Comments
nonearther@lemmy.ml · 32 pts · 2y
The only version management I believe in is Nver.
I write code once and then leave the project completely. Start with 0.0.1 and end with 0.0.1
lars@lemmy.world · 2 pts · 2y
Because git doesn’t require, but could definitely benefit from, empty initial commits, my go-to is:
which is completely Nver- and Y2K-compliant
xmunk@sh.itjust.works · 13 pts · 2y
I support 0ver, my open source project is currently at 0.1.9 - I'm looking forward to releasing 0.1.10 as I continue to avoid the precious 0.2 mark when I become feature complete and open the project up to a wider audience. I assume 0.3 will be a full source rewrite when I achieve Google Scale.
HairHeel@programming.dev · 7 pts · 2y
Is gmail still considered beta?
sxan@midwest.social · 4 pts · 2y
It's funny. With Go modules, though, there's a very real consequence of moving to 1.0.x; the build system starts imposing different constraints. Same with the move to 2.0.x. Changing versions means more than just throwing a tag in the VCS.
Most of the time, it's what you'd do anyway and isn't a bother. Sometimes - not often, but non-zero - it's an imposition.
gabmus@lemm.ee · 2 pts · 2y
To be completely serious for a moment, conventional commit + what-bump is really useful for doing semver