Comment Invest in book publishers now! (Score 1) 575
Its time to throw-away/rewrite a lot of books out there! Some very old.
Comment Re:And this is news? (Score 1) 270
I guess you're from old school!
Comment Re:DDOS (Score 4, Insightful) 631
Or another ship cuts the trans-Atlantic internet cables.
Or a power cut that takes out your router.
Or someone adding a wireless router in the same channel as the one you are using.
Or microwaves/other device/weather interfering with the wireless signal.
Or
Comment Re:Another reason not to fly via Heathrow (Score 1) 821
Terrorist related deaths are low due to our governments taking initiative and putting up security measures like these body scanners.
Comment This should be on failblog! (Score 1) 342
http://www.failblog.org/ 'nuf said.
Comment STFU, you Microsoft shills! (Score 3, Insightful) 498
So, when Microsoft makes so much noise with press adverts & getthefacts campaigns, its 'marketing' and when FOSS supporters rejoice they are 'fanatics'!! Just STFU and get back to your windows 7 house party.
Comment Re:Where's India's domestic economy? (Score 1) 1144
Whats wrong with crapping in the fields? Please explain.
Comment What about the women? (Score 1) 193
This is a very sexist study to talk about only man's guts!
Submission + - SPAM: Wine 1.0 Release Criteria updated
twickline writes: "On March 15th Dan Kegel sent a email to the wine-devel mailing list with a outline of the new release schedule for Wine 1.0
Alexandre Julliard replied with his thoughts on the first draft with some suggestions.
We need a code freeze and stabilization period before the release. My thinking is that we should have a 1.0rc1 release, probably sometime in May, and from that point on only accept small obvious fixes. Then we'd have rc2, rc3, etc. as needed until the bug list gets small enough. And by rc1 (or even earlier) any bug that requires more than a small simple patch would be deferred to 1.1.0."
Link to Original Source
Alexandre Julliard replied with his thoughts on the first draft with some suggestions.
We need a code freeze and stabilization period before the release. My thinking is that we should have a 1.0rc1 release, probably sometime in May, and from that point on only accept small obvious fixes. Then we'd have rc2, rc3, etc. as needed until the bug list gets small enough. And by rc1 (or even earlier) any bug that requires more than a small simple patch would be deferred to 1.1.0."
Link to Original Source
