slip endlessly, and no-one cares to fix bugs in a hurry because - well,
lets just slip the schedule instead :-) Also, the decision to when, how,
and by how much to slip the schedule is some particularly poisonous
problem.
I'm aware that a Release doesn't have to be bug-free (is there any
bug-free program? :) ) but since LibreOffice is trying to get momento
over OOo it should make damn sure that AT LEAST it doesn't have more
bugs than the "competition" ;)
Our first release: 3.4.0 is planned to be as buggy as the developers
let it be: ie. all bugs not fixed by the time we release will be seen
live :-) if any are serious - then we can release note them of
course ;-)
Naturally, our 3.4.1 release will be better, and by 3.4.2 we will
exceed the quality of any existing release from anyone (at least, that
is the plan), by 3.4.3 we'll be in some fantastic zone of stability and
so it goes.
This was the plan with 3.3.x - and (so far), it seems to be working
rather well; I think it will be the plan for 3.5.x too.
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.