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



On Thu, 2012-08-09 at 12:53 -0700, bfo wrote:
If I may propose anything, please add:
- zero tolerance policy for regression issues during development
- zero tolerance policy for crash issues during development

        So - incidentally; we already have something like this in place. If you
can find a regression or crasher running a master build **that is not in
the last stable release** - you are encouraged to mail the developers
list with it. ie. we want to find out about regressions ASAP while the
work in a given area is going on. Of course - that makes it necessary to
run a master build - please do :-)

I was seriously amazed after reading Most annoying bugs section
of Release notes for 3.6.

        Right; the near-zero-tolerance change here is intended to encourage
developers / QA / bug-reporters to rebel against the all-too-common
"just delete your profile" -> "it works" -> WORKSFORME resolution cycle
that we see.

        And yes - time based releases means that (while we slipped a week to
try to fix it), 3.6.0 is really not as good as we wanted; that is
certainly true. On the other hand giving all developers the idea that
testing / bug fixing can be endlessly deferred since we'll never release
- is a really poor plan too; one aspect of that is that it's not fair on
the people that work diligently to test and fix things so we can release
at a given time.

        ATB,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.