Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index



Noel Grandin wrote

- zero tolerance policy for regression issues during development
- zero tolerance policy for crash issues during development
People who advocate zero tolerance for such things are welcome to 
provide the time and financial resources necessary to achieve this.

Hi.
Or maybe change in the base code workflow is needed? 
1. design the change
2. find out which modules are affected
3. plan testing
4. code
5. prepare unit tests
6. careful code review (not just OKeying)
7. commit in the unstable branch
8. QA confirm
9. commit in the stable branch
I think many bugs introduced are an effect of omitting one (or more) steps
from that list by the developer.
Using best coding practices always would help a lot.
Maybe gerrit will help to achieve this in some way...
Best regards.




--
View this message in context: 
http://nabble.documentfoundation.org/minutes-of-ESC-call-tp4000217p4001027.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.