Hello Michael, Kohei,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I feel extremely uncomfortable (personally) introducing a couple of<br>
thousands of LOC change between RC1 and final for 3.4.2. We're in a<br>
triple review mode because our changes will not get much testing before<br>
they are unleashed on tens of thousands of new people per day.<br>
<br>
I'd prefer to see this slip into 3.4.3 (personally) - shame if the<br>
problem is there, but the chance of regression seems high - even though<br>
the code is nice and clean of course :-)<br>
<font color="#888888"><br></font></blockquote><div><br>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.<br>
<br>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.<br>
</div><br>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.<br>
<br>Regards,<br>Markus<br></div><br>