[development] Re: 18 critical bugs left

Moshe Weitzman weitzman at tejasa.com
Wed Mar 8 21:51:46 UTC 2006

>>1) no one should go off closing 4.6 issues just because the bug has
>>   been fixed in 4.7 ;)
>>2) we should all be clear what the policy really is.  i think it can
>>   be summarized as:
>>   - new features only happen in a development release, no matter
>>     what.
>>   - bugs are fixed in all branches where they can be reasonably
>>     fixed, if someone does the work to create and test the patches
>>     and the core committers agree it's worth the trouble.
> - bugs should be fixed in a way that does not require database changes. Only 
> for security issues we allow minimal changes in the database.
> Or am I wrong?
> Bèr

darrel's statement is as clear as can be, and dries has confirmed it. 
lets not restart the discussion. i'm guessing ber hasn't finished 
reading the thread.

More information about the development mailing list