Linux Kernel 3.1 RC 2 Released
sfcrazy writes "Linus Torvalds has announced the release of Linux kernel 3.1 rc2. He said '300+ commits for -rc2 is good, but please make me even happier for -rc3 by ONLY sending me real fixes. Think of it as "fairly late in the -rc series," because I really want to compensate for the merge window being fairly chaotic.'"
What's with all the slashdot users recently, going fucking stupid about version numbering? Who cares what the versions are called: 3.10, 3.11.30 3.A03930. As long as the software works and the users (developers and end users alike) are able to interact with the software, what's the big issue?
I hate to break it to you, but there are many of us here who work professionally in the IT field. We don't have the luxury of being students such as yourself.
When you have to manage 80,000 or more desktops and servers, spread around the world, things like version numbers become very important. It's not so much the numbers themselves, but the expectations and facts that they should convey.
Responsibly using version numbers lets the software developers convey to us, the software administrators and users, important knowledge about the software they have created, and how it relates to earlier and future releases.
A major version number increase should signify massive changes. It should indicate to us that we should disregard any previous knowledge we have, and learn the software product from scratch. It indicates to us that we may need to provide extra assistance to the employees using the software we're tasked with administering. Do you get the idea? Are you beginning to follow what the real world is like? Yeah, it's not like what your computer science professors may have caused you to believe.
When projects start changing major version numbers without good reason, it makes us unsure about such projects. We lose the ability to predict how much of an impact upgrading will have, for instance. Worse, it gets executives asking questions. Even though Linux 3.0 is only slightly different from the last 2.6.39, the major version number jump makes some executives worry unnecessarily. They start to think that what's nothing more than a routine upgrade is more risky than it is.
I have colleagues in IT who have experienced similar problems with the recent Firefox debacle. They have to deal with users who don't want to upgrade from Firefox 4 to Firefox 5, thinking there will be major changes and adjustments, while there's almost no noticeable difference between the two "major" releases!
It hurts the adoption and acceptance of open source software when major projects start playing dumbass games like these with their version numbers. It does indeed create the so-called "FUD" for those who make decisions regarding the use of open source software.
You are so ignorant you must be another student. Not the grand parent but some of us *do* pay for open source software. Out side of academia most people don't have the liberty of seat of your pants forum and IRC support when shit goes seriously wrong. Got a linux kernel bug? Your Redhat support contract may (if its serious enough) get Alan Cox on the phone (did some years ago, I realize he has now left Redhat). Got a table that is being completely mis optimized? Your Maria contract will get you Monty. I could go on and on. Open source software isn't just about free software for kids who think patents are yucky and everything should be free, its about quality software through open community development. Version numbers matter, they matter to executives, they matter to ignorant users who fear upgrades. They matter to those who pay those support bills and vendor contracts that fund open source software development.
-- Don't have 80k Linux desktops, but I do have 35k and growing Linux servers