Lots of regressions in games in last few versions

[Vitaliy Margolen]

Alexander Dorofeyev wrote:
> Vitaliy Margolen wrote:
>> If developer can not tell if this is a hi risk or not, then such patch 
>> have to be marked as hi risk and should not be accepted while we are in 
>> the code freeze. Unless number of people test this patch on different 
>> hardware with different software and verify it's functionality.
>>
>> We add more and more features to d3d which is wrong. This is exact point 
>> of code-freeze to accept low rusk fixes only.
> Some of those changes that date back to 0.9.58 or so obviously happened before 
> the commitment to code freeze.
> 
> But I think that testing and reverting any patches submitted during code freeze 
> that cause d3d regressions and can't be fixed real quick is a good idea.
> 
They have to be fixed. That's the point. And if it takes big changes to fix 
it, then those patches have to be reverted.

Again I'm not talking about what should have been done or that some one 
missed something pretty big. That's the way development goes. I'm talking 
about the same thing Alexandre said - if we have a regression that can not 
be easily fixed the patch that caused the regression have to be taken out.

Also no more additional features that open up a can of worms! No more 
additional caps that all games starting to use! (until after 1.0)

Vitaliy.