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


Hello Michael, Kohei,

       I feel extremely uncomfortable (personally) introducing a couple of
thousands of LOC change between RC1 and final for 3.4.2. We're in a
triple review mode because our changes will not get much testing before
they are unleashed on tens of thousands of new people per day.

       I'd prefer to see this slip into 3.4.3 (personally) - shame if the
problem is there, but the chance of regression seems high - even though
the code is nice and clean of course :-)


I understand your concerns but in my opinion the current situation is even
worse. I think we will call 3.4.2 ready for enterprise use but calc is
limited to simple documents because complex documents need some minutes to
load and most people won't expect that. Even worse I read several comments
on the german user list reporting that they think calc freezes when you load
complex documents and suggest to stick with 3.3.

I think we can't expect from an enterprise ready version that you can't load
complex documents. I know that we may introduce problems in some corner
cases but it will be even worse if we can not work in normal use cases with
complex documents.

So I think the question is how important it is to be absolutely safe that we
don't include any bug when we fix a serious problem. In my opinion in this
case the fix for the bug is more important but others might have different
opinions here.

Regards,
Markus

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.