Slashdot Mirror
Microsoft's Lack of Nightly Builds For IE
Ricky writes "Many wonder why Microsoft doesn't offer nightly builds of Internet Explorer — or at least something more frequent than months-to-years. Ars talks with Microsoft's general manager for IE, who says the IE9 development cycle will look much the same as previous versions. Not a great idea."
WTF? Most companies don't release nightly builds of their software. Why on earth are we singling out Microsoft, and only one of their products at that? Infrequent releases are the norm, not the exception, and while you may argue that it should change, it's ludicrous to single out one program among thousands for following the standard practice.
"16MB (fuck off, MiB fascists)" - The Mighty Buzzard
The better question would be why Ricky believes not releasing nightly builds is "not a great idea". What part of Microsoft's standard development cycle would benefit from nightly builds? Why would Microsoft decide to release nightly builds, which are inherently unstable, to a public that loves to pick on MS for producing unstable software? Why would MS risk some bored journalist writing a hit piece on IE 9 based on a particularly faulty nightly build just on the off chance someone out in the ether might give them some useful feedback on it?
In short, why the hell would they release nightly builds?
Shitty article. Nothing to see here....
It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
"Many wonder why Microsoft doesn't offer nightly builds of Internet Explorer."
Whoever "Many" is, they seem to always be interviewed by Ars and FoxNews.
As somebody who has frequently participated in beta tests of lots of software, including Microsoft's, this is spot-on. Sure, their infrequent betas get some good feedback and some good bug reports, but they also get absolutely drowned in a deluge of people on the discussion boards (newsgroups, actually) who complain about:
A) Nothing particular at all, they just signed on to complain.
B) Stuff that's completely unrelated to the beta (such as a complaint about IE6 on the IE8 beta discussion)
C) Stuff that's completely unrelated to the product (complaints about Excel on the IE8 board)
D) "How dare Microsoft release [a beta of] this product with such-and-such [known, sometimes in release notes] bug!"
E) "WTF I installed the latest version of X, and now I can't access my Y, so I'm switching to competitor Z and never buying anything Microsoft again!"
F) Complaints about Beta 1 bugs during Beta 2 or RC test phases.
G) Complaints from people who installed the software on a production machine, and expect Microsoft to provide support for it.
These are the types of morons that Microsoft has to deal with. I've seen some of this type of behavior in other betas, to be sure, but some of the problems, especially D, E, and G, are most common on the MS betas. People just seem to expect that any code from MS will be production-ready and expects the company to stand behind their software as though it were a released product.
Microsoft would be *insane* to release nightly builds to a group like that. A closed beta nightly program, maybe (participants culled from those who are actually useful and productive on the public beta) but certainly not open. Especially considering point F above; people already can't always keep up with the pace of the infrequent releases, and asking them to identify the build number they're using would be an exercise in futility for far too many.
There's no place I could be, since I've found Serenity...