Well, that last one was so much fun that I checked out the rest of h-online.
As befits Autumn, or Fall if you prefer, it is a field ripe for the picking.
I’ll leave you with this true FUD, which depicts an awesome future of “Yeah, brothers, it will now work!” Particularly when “working” involves really complex stuff like adhering to WiFi standards and general networking and the like.
What I really admire is this:
“One week after issuing Linux 3.1-rc1, Linus Torvalds presented the second release candidate of Linux 3.1 late on Sunday night.”
Can somebody please explain to Mr Torvalds what a “release candidate” is? Clue: you don’t turn them over in seven days. I don’t care how many billion eyes you have. This is Not Good Practice.
Please don’t take my word for it. Read it yourselves. It’s a giggle-fest. Here’s a taster, though:
non-functional and only intended for testers and developers.
It gets even funnier after that.
——————————————
And note, btw, that the Tech Fantasist in question hasn’t actually tried any of this crap; he just takes it at Torvald’s word.
Par for the course.
——————————————
And eventually this awesomeness will percolate through to downstream. Just don’t hold your oneiric, natty, maverick, lucid, karmic, jaunty, intrepid, hardy, gutsy, feisty, edgy, dapper, breezy, hoary or warty breath.
Because, when it eventually does, downstream will have broken the damn thing anyway.
Comments
I guess Torvalds doesn’t believe in the Wikipedia
“The term release candidate (RC) refers to a version with potential to be a final product, which is ready to release unless fatal bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug.”
Six weeks, man. Six weeks. Minimum.
And of course we have no idea where the alphas went. This one is presumably beta.
What “alphas” and what is this talk of “RCs”, seriously guys, It’s FOSS, just FixItYourself™ already.
I mean, I don’t even…
Wow, it got new drivers and some new draft code. A+ for draft standards for mesh networking. I totally care.
“Because, when it eventually does, downstream will have broken the damn thing anyway.”
It’s the open source way, and it’s different.
In the real world, we’d have just called that “shifting blames”, but whatever.
@Chris:
Ah, but that’s just “Part 1: Networking.”
Wait for “Part 2: Introducing 'Come Froms’ to the Kernel.”
Much more chewy, that one.
You must be signed in to leave comments.