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


https://bugs.documentfoundation.org/show_bug.cgi?id=116944

--- Comment #21 from Lionel Elie Mamane <lionel@mamane.lu> ---
(In reply to Florian Reisinger from comment #15)
If you care to explain why

- removing a DB backend without deprication notice
- keeping the HSQLDB data in the ODB file WITHOUT possibility to open it
with an old version of LibreOffice
- hushing the transition to the new database backend

is a good idea.

It is not, and will not happen. Please, there was some over-enthusiasm, things
got committed to master, they were discussed and the plan was established. Do
not take every commit to the master branch as a firm, well thought out, plan.

Let's stop excoriating this transitory situation and focus on the reasonable
plan.

- Putting it in the 6.0 release notes is impossible - already released.
  --> Mark it for removal in 6.1 with removal in 6.2 / 6.3

My current thought is: deprecation when Firebird is in good shape (cf the
tracker bug for that), and removal at least one major distro LTS cycle after
that.

  --> New databases will be created with Firebird (by default?) in 6.1

_If_ the Firebird driver is in a good enough shape, which we have good hope it
will be.

- Why keep the old data in the file?
  --> Creating a new file with just Firebird data makes more sense as the
end user is not able to recover the data!

Yes.

- Why do we need to get rid of HSQLDB so quickly?

We don't.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.