Linux 3.0 Release Delayed
JustinRLynn writes "A recent Google+ Post by Linus Torvalds indicates that version 3.0 of the Linux kernel will have to wait due to the discovery of a 'subtle pathname lookup bug.' Linus indicates, 'We have a patch, we understand the problem, and it looks ObviouslyCorrect(tm), but I don't think I want to release 3.0 just a couple of hours after applying it.'"
Project Manager: Did it build?
Developer: Yea, but we haven't even run the thing yet
Project Manager: Ship it!
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
I say push it live, let those damn n00bs grow some chest hair by referencing all their files by inode id.
There's no -1 for "I don't get it."
Your project managers make you get a completely clean build before you ship? How do you guys stay on schedule?
No problem. I'll just run GNU Hurd.
The shareholders will demand an answer for th ... wait.
There's a spot in User Info for World of Warcraft account names? Really?
Waiting for someone to take this as Linus Torvalds' recommendation of Google+...
No, only firefox does that.
I think the more important news here is - Linus uses Google+ for announcements now?
Facebook really is in trouble now.
You are confused. This is the Kernel, not Firefox.
BTW: I heard the guys at Mozilla are working on a new feature: The ability to change the version number while the browser is running. That's real progress.
WTF am I doing replying to an AC at 5 A.M on a Friday night?
I don't know what commercial environment you've been in, but in the places I've worked, release becomes hell because you have your bug list and someone (read a commitee) has gone through and labeled the "show stoppers" which are bugs deemed important enough to be fixed before the software can be released, and because of politics in the commitee, all but the most trivial become show stoppers. Upon fixing the last show stopper, the software then needs to go through regression at a minimum, and usually a complete test suite before it's allowed to be released. And even then, that goes into system integration, where the whole process starts again.
Your project managers make you get a completely clean build before you ship? How do you guys stay on schedule?
Simple enough, Firefox style: Any time you get a semi-clean build, you tag it. When you release, you simply bump the version number of the last tagged build. So what if you don't get half the features - it's a new version, as witnessed by the version number!
Yes but that feature has been delayed until the release of Firefox 7, so you will have to wait a week.
Make SELinux enforcing again!
Sadly, I don't understand the explanation or what the patch changes.
https://lkml.org/lkml/2011/7/17/103
https://lkml.org/lkml/2011/7/17/103
[Posted by Theovon earlier, but I prefer a clickable link.]
That depends on the balance of power in the organization. If sales/marketing have the bigger share of the power, QA is downsized or eliminated and the only "show stoppers" are unchecked feature boxes.
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
I for one am glad a geek IS the project manager.
More focused on getting it right than meeting deadlines.
That would explain why GNU/Hurd is such an excellent OS
For everything besides committing, Git is horrible
It would be nice to know what you had a problem with. People here could perhaps enlighten you as to why things aren't working out for you, or you could enlighten them as to why git is inferior. It has its flaws (chiefly obscure error messages), but I've found it a better fit than cvs and svn.
Recently.
Nerd rage is the funniest rage.