3 ms·
>> Due to our size, we don’t need any kind of backwards compatibility, we just update everything. > Then just use 0.y.z versions and be done with it? FWIW, I
by pgwhalen 5y ago
>> Due to our size, we don’t need any kind of backwards compatibility, we just update everything.
> Then just use 0.y.z versions and be done with it?
FWIW, I also work in an organization that thinks of libraries this way, and we've found success and simplicity in versioning (for production) our Go libraries as 0.X.0 where X is just a monotonically increasing number generated by the build pipeline.
- mananaysiempre 5y ago... Zerover[1]? [1] https://news.ycombinator.com/item?id=28154187 https://news.ycombinator.com/item?id=28154187
- pgwhalen 5y agoYep! I think it's fair to needle open source software, but it absolutely makes sense for a lot of internal development to adopt this sort of versioning policy.