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


Hi,

I read the whole thread and tried to understand, "tried" because I'm not
enough "fluent" in these technical/internal LO part.

Why A2B must be quickly (I mean without waiting for next LO version)
"upgradable"?
Either it's stable and so we don't absolutely need to upgrade it quickly or
it's unstable and therefore it shouldn't access to LO core parts anyway.
In first case, A2B could be bundled extension, in the second case  a simple
extension because there'll be fix upgrades to become stable (or at least
"enough stable").
So if A2B can be considered as enough stable and therefore can be a bundled
extension, it means fixes from A2B can be included in the different versions
(not only major) from LO 4.3.1, 4.3.2, etc. (like external libs)

Now about new LO version which would include last patches from A2B compared
with old LO version, yes companies should upgrade in this case or they're
still have the possibility to build LO from the sources with the required
patches, they're free to do it as we're free to try to harden LO a bit.

In conclusion IMHO b534967caca6767cd2100da363b1da2433640ddd should be
reverted.

Julien



--
View this message in context: 
http://nabble.documentfoundation.org/Access2Base-New-release-tp4108421p4112581.html
Sent from the Dev mailing list archive at Nabble.com.

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.