I think its better to think of it like a president or prime minister. He might set the plan and direction and making the big decisions, but there are thousands of others supporting and making the plan actually happen.
In the past he has delegated the release to others as well.
So if the worst would happen, the linux project would continue operating fairly seamlessly.
It's also mind blowing to consider that as many other projects, both Linux and Python started as a hobyist project never meant to do more than cater to some personal needs.
This taught me how important is allocating time for your team for their personal projects, as the next school romance anime tagging system could be the cornerstone of every AI in the future.
Except 99.999% of personal projects won't be that popular and allocating time for personal projects is a waste in that regard. Basically you'd be playing lottery and not get anything out of it.
There's plenty of reasons to encourage personal projects, but this isn't one of them.
That's because it doesn't : ) He is the top level engineer/manager for releases and technical consultation but there are many more engineers "under" him leading and moving the pieces into place.
The kernel will figure something out. There are already lots of companies investing their own development resources into it. Would just need a new leader to emerge. Perhaps it'd be a rotating group of people who are responsible for managing a single release.
Tons of smaller but important projects don't have this luxury, though.
I blame browsers for their out of control versioning.
Chrome is on version 118 now and gets a bump roughly every 6 months. Firefox is 4 years older, yet they started following the same rapid versioning at version 5 to "keep up" with Chrome which was already on version 12 but a younger browser.
2011 is actually the same year Firefox started their rapid versioning to try and match Chrome. There was definitely a shift in versioning styles around then.
"So this last week has been pretty calm, and I have absolutely no excuses to delay the v6.6 release any more, so here it is," Torvalds wrote early on Monday morning, as version 6.6 debuted as planned.
Among the highlights of the release are the KSMBD in-kernel server for the SMB networking protocol, which adds additional features for sharing files and improving inter-process communication in Linux, hopefully speeding I/O.
Speaking of AMD, early tests by the Linux-lovers at Phoronix found substantial performance gains for its manycore "Bergamo" CPUs thanks to the inclusion of the Earliest Eligible Virtual Deadline First (EEVDF) scheduler.
The kernel also added support for AMD's Dynamic Boost Control tech that allows users to tune Ryzen CPUs for optimal performance.
A change to this cut of the kernel rebrands it as just "SELinux" – a reaction to the Agency's role in ops that have harmed privacy, per Edward Snowden.
US-based contributors will also have a Thanksgiving-sized hole kicked in their schedules, making it possible work on this release will be slow and Torvalds could push it into early 2024.
The original article contains 506 words, the summary contains 181 words. Saved 64%. I'm a bot and I'm open source!