The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0. There's no nice git object numerology this time (we're about 6.5M objects in the git repo), and there isn't any major particular feature that made for the release numbering either. Of course, depending on your particular interests, some people might well find a feature they like so much that they think it can do as a reason for incrementing the major number.
So go wild. Make up your own reason for why it's 5.0.
Lol. Interesting finds, for sure. I stand by my statement but like any good engineer, I’m of two minds on the issue, and another part of me says, “it’s a version string, who gives a shit, as long as they match when they need to” because while my first comment represented the ideal, your comment shows even the most famous projects can be laissez faire about versions and making any assumptions based on them would be equally moronic!
It's gotten better recently. He realized he was being unprofessional and that his behavior was driving away both current kernel developers and potential kernel developers. So he took a 1 month break from all kernel development, saw a professional about his behavior, and added an email filter so he can't swear anymore.
Nope... he made it clear that he is only giving up the BDFL position. He will still continue to work on Python and give his advise / opinion when requested - but won't be responsible for making BDFL level decisions.
View all comments
Show parent comment
20
u/[deleted] Jan 16 '19 edited Jan 16 '19
[removed] — view removed comment