Hi there, just picked two mails from this thread more or less randomly, as they show some common pattern:
Peter Hillier-Brook wrote: > Given that the release of LibreOffice 3.4.2 is targeted at > enterprise users, I find it surprising that the product is thought > to be ready for release. At lease 2 significant bugs have been > introduced and remain present that would, to my mind, discourage > personal, let alone enterprise users. > Software quality is a somewhat fuzzy area, and one that is perceived very individually, usually. The bugs you list are no regressions from the previous 3.4 version, so by definition, since 3.4.2 fixes many other bugs, it's better than 3.4.1, which in turn was better than 3.4.0. Generally, assessing whether a specific version will be suitable for your company, or home use, is an individual decision - now, yesterday, and back in the day with OpenOffice.org. You'll always end up deciding if you need this nice new features, or whether the new mail merge wizard is broken so fundamentally that you can't use the version. Of course, for companies deploying LibO, we recommend getting professional support, that allows you to get *your* bugs fixed in time. You've quite a choice there, another advantage of having a more diverse ecosystem. plino wrote: > BTW I still don't understand why this enterprise release jumped Beta testing > and went directly to Release Candidate... > Because the amount of changes relative to 3.4.1 was tightly controlled and relatively small. Let me outline the process here a bit: * major code line approaches initial release - that requires a set of betas * initial release of a code line (e.g. 3.4.0) happens, more bugs are found in production use (that curiously don't turn up during beta/rc phase - an observation we've made also during OOo times) * the bug fixing on that code line continues (usually guided by bug severity, but of course also by specific customer demands - e.g. one of the participating companies' customer escalates a bug, company fixes it, fix goes into next bug fix release) * translation / help updates continue on that code line * frequent bugfix release on the code line happens (3.4.1, 3.4.2 etc). Code only enters that code line after review, no new features are allowed. If something regresses, usually the fix is simply reverted. * bugfix version gets released, usually after two release candidates are published. * more bugs are fixed on that code line ... HTH, -- Thorsten -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
