Carlo Strata wrote:
That bug is not even fully analysed, let alone fixed yet - so why
should we even start pondering to delay a release of an otherwise
You are right, but this one is the only one I read about in these
days and that is a regression...
I'm sure there are some other ones ("3.4's most annoying bugs")...
sure - but either there's a safe fix, that the responsible devs have
been poked with & that got cherry-picked in time for -3-4 - or
there isn't. Probably all I want to say is that your mail comes
some 2-3 weeks late - please remind people to review fixes before
release tagging happens.
As many others have said before, the point of time-based releases is
to get fixes shipped to users, instead of being caught in that "just
one more fix" dead-lock.
Nothing prevents us from doing another release from the libo-3-4
branch next year, and surely over the time, this branch will
acculumate more useful fixes than just this one Calc bug.
I say this because Rainer (Bielefeld) told me (on September the 1st,
2011) that TDF are fixing all bugs in Master trunk (3.5) and cherry
pick something good for 3.4's releases... This means that 3.5 may be
better than any 3.4 is now and will ever be.
Absolutely! That's the whole point in development, to make a better
Unsubscribe instructions: E-mail to firstname.lastname@example.org
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
Impressum (Legal Info)
: 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