[Tickets #6207] Re: Collection of upgrade scripts

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=6207
-----------------------------------------------------------------------
 Ticket             | 6207
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Collection of upgrade scripts
 Queue              | Horde Base
 Version            | 3.1.3
 Type               | Enhancement
-State              | New
+State              | Feedback
 Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-02-04 23:37) wrote:

So, given that these are for Horde 3.1.3, which isn't even the latest
stable release, and we are currently at RC-2 for Horde 3.2.0, and 3.1.x is
therefore only maintained for security fixes, what do you see us doing with
these?

I very much appreciate your contributing what you have, but it's
frustrating to get workarounds for bugs in old versions, instead of direct
bug reports that might (or might not) still be relevant.

Any work you'd like to contribute on migrations or similar functionality
would be quite welcome. If you are interested in it being included in the
mainline distribution, however, I encourage you to ask questions on the dev
list (http://horde.org/mail/) instead of working around APIs that aren't
clear. The docs are certainly an issue, but we're friendly an answer
questions.

A final note - the reason Horde's upgrade scripts avoid direct database
access when possible is that allowing non-SQL drivers is central to Horde's
design and philosophy. So scripts that ignore other backends are not likely
to be featured in the core.