4 ms·
... hubris? I think that's a bit much. We went v1 once we decided our software was ready for other people to use. It meant we'd ensure compatibility via upgrad
by julianlam 5y ago
... hubris? I think that's a bit much.
We went v1 once we decided our software was ready for other people to use. It meant we'd ensure compatibility via upgrade scripts, and it meant we wouldn't do irresponsible things like tell users "this release requires you to drop your database and start over"
- k__ 5y agoI think, that's the main problem with SemVer. Everyone tries to merge the major version with some kind of nebulous "readiness". While it should just be a number related to technical aspects of the software.
- superjan 5y agoAnd I think that is the right way to think about it. I think people stay on 0 because they think they have to implement all ideas and edgecases before it you can call it 1.0. You can also get stuck on 1.x releases in the same way (notably Java).