I do use SemVer but I kinda feel like there's gotta be a better system out there. Issue number 1 with it is that I see devs stay on major version 0 for a very long time so that they can keep not worrying about whether updates are backwards compatible. Biggest example I can think of is FastAPI, which is currently on 0.110.1. Issue number 2 is that because it's a value judgment what's a feature and what's a bugfix, it can't really be incremented programmatically. Which leads to programmers forgetting to update the version properly in some cases, or classifying updates as patches or vice-versa. I feel like a better SemVer would be very precisely defined to avoid some of these issues. "Production ready" is subjective but "publicly released" is not. "Substantial functionality" is subjective where "API change" isn't.
Hey Arjan, big fan. Can you cover Feature Flags in software development, I'd really like to know all the implementation and the behind the hood working of it.
@@TheWolverine1984 I think if a number is 2 digits, it's considered a whole number and it is not considered a decimal number so 1.0.15 > 1.0.2 because when you reach 1.0.9 and you need to add 1, what else would you do if your change is still a patch? you just add 1 and treat it as a regular whole number
I've always wondered if these numbers mean something or just some random lucky number that the dev team throws away, makes more sense now lol thank you, we need more of these short videos..
We are using semantic-release which lets you automate your release workflow and uses semantic versioning. It can also be coupled with conventional commits which is already awesome on its own. Maybe you could check both out in a follow up video :)
Hi Ajan, I use server manually :S I would like to know if is possible to automate with some tools in my process release, ike put in poetry or hatch or I dont' know. Any tip or suggestion will be appreciated
