Sorry, but do NOT release things until they're done. If released in an unfinished state, they basically have erected the cross and handed the community not just themselves but also the rusty nails and hammer we'll use to crucify them.

So no. Keep it inhouse until it's thoroughly tested, and when it's good enough, THEN release it. Rushing the release is what landed things the way they did, and some parts of history should not be repeated.

...this is a beta or will be, better said...A BETA patch is an unfinished and open for development product. Ok to get some feedback from people then when ready to be put up to Steam!...nothing wrong with that!..COD is after all an evolving project!

Agreed, only a BETA, no commitments or broken promises as it is not a finished product, but something we, the community can help with!

To bad its impossible to make this community understand the meaning of the word "beta" or "VIP" for that matter. You might as well try to explain the inner workings of a combustion engine to a 3-year old.

They have time and time again said that this patch is for the graphics engine only. What do you think will be the first question after its released?

Heres a hint, why...isnt....the...AI....fixed.....?.....?....? or any number of other issues people have that ISNT connected to the graphics engine.

And you think releasing anything thats other than perfect, or as close to it as possible, won`t create a nuclear meltdown NO MATTER what they say before release.

Personally i think the patch have been ready for the last week or two, they just dont want to release it before all the team members had a chance to put thire personal affairs in order, you know, writing a will, signing over the car to the misses and so on.

Yes, but I thought I detected a late surge for the Yes campaign. If that was sustained then who knows?

Democracy is over-rated anyway.

Nice one Baron!

YESSSS! It will be released soon :)

nooo... the general feeling is; a few (very few) people are fed up waiting

Deja Vu, deja vu.

your argument is null and void seeing as how they didnt follow this rule to begin with...at least if they release the BETA patch, it would have the word BETA attached to it....

if they release a beta patch, its the users choice to download it or not...why delay testing on the community which you know they will end up doing anyways...

it would also be a good way to test the new bug tracker....

but of course giving the user a choice, and optional download, is no good for anyone....even those who dont want it could simply choose to not download it they would rather impose their own views on others, and have it so NO ONE can download it....what a joke...


edit i keep seeing "dont release it till its done" so following this train of though, releasing anything beta is a no no?? i mean its not like they followed this rule to begin with...i mean the DAMAGE IS DONE...releasing a BETA patch to the community, isnt the worst thing they could do...i guess you people who say "dont release it till its done" refused to download the previous beta patches...i. suppose you people refuse to download beta patches that hotfix an issue, cuz the nature of beta implies that its not finished...unless you refuse to download all kinds of "beta" releases you are nothing but a hypocrite, and probably a fanboy...

Why do people always assume that there is an 'it' to release? With a project this complex, it is highly unlikely that there is always a single ongoing 'current development version' of the software while it is being worked on. Instead, a (relatively) stable prior version will most likely be used as the base for revisions, and only when a new 'beta' is required will the revised software be compiled as a unit - at which point, it isn't a 'beta', but an 'alpha', until it is confirmed that there aren't (too many) new bugs introduced by the interactions between different changes.