Changes

Line 21: Line 21:  
** Non-regular patches should be formed in [[Features]]. These patches might take several tens of K. This is by design; that it is hard not only to develop, but also to review and it should involve several committers for a reasonable amount of time. [[User:Alsroot|alsroot]] 09:28, 25 October 2010 (EDT)
 
** Non-regular patches should be formed in [[Features]]. These patches might take several tens of K. This is by design; that it is hard not only to develop, but also to review and it should involve several committers for a reasonable amount of time. [[User:Alsroot|alsroot]] 09:28, 25 October 2010 (EDT)
 
** Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied [[User:Alsroot|alsroot]] 09:33, 25 October 2010 (EDT)
 
** Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied [[User:Alsroot|alsroot]] 09:33, 25 October 2010 (EDT)
 +
** Purism is good but there is no need to achieve it by single patch, it might be changed in post-commit patches if second reviewer (e.g., looking to the patch thread on mailing list) found an issue in already commited code. [[User:Alsroot|alsroot]] 13:39, 25 October 2010 (EDT)
 
* officially dropping support for 0.86? (e.g. {{bug|1838}})
 
* officially dropping support for 0.86? (e.g. {{bug|1838}})
 
** do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 
** do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)