[asterisk-dev] Deprecation of cdr_mysql

[Olle E. Johansson]

11 jul 2012 kl. 16:50 skrev Matthew Jordan:

> 
> 
> ----- Original Message -----
>> From: "Olle E. Johansson" <oej at edvina.net>
>> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
>> Sent: Wednesday, July 11, 2012 9:43:26 AM
>> Subject: Re: [asterisk-dev] Deprecation of cdr_mysql
>> 
>> 
>> 11 jul 2012 kl. 16:38 skrev Mark Michelson:
>> 
>>> On 07/11/2012 09:02 AM, Paul Belanger wrote:
>>>> On Wed, Jul 11, 2012 at 9:47 AM, Olle E. Johansson
>>>> <oej at edvina.net> wrote:
>>>>> I must have missed the discussion - can someone please explain to
>>>>> me why cdr_mysql is marked as deprecated in 1.8?
>>>>> 
>>>> It started with this review[1] and turned into this wiki page[2]
>>>> 
>>>> Basically there is a better way to do it (ODBC) and nobody wanted
>>>> to
>>>> maintain the module.  After Asterisk 11 drops, I suspect you'll
>>>> see
>>>> some patches starting to remove some of the deprecated modules
>>>> from
>>>> source.
>>>> 
>>>> [1] https://reviewboard.asterisk.org/r/1181/
>>>> [2]
>>>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
>>>> 
>>> 
>>> Let me chime in and say that removing deprecated modules is
>>> unlikely to occur unless we have a suitable drop-in replacement
>>> that we are willing to support.
>> The wiki page states a bit more, that if someone claims to still have
>> it in production and have arguments against the suggested
>> replacement, we should reconsider.
>> 
> 
> If there is functionality that cdr_mysql provides that cannot be
> provided by cdr_adaptive_odbc, then I think that's grounds for moving
> it from deprecated => extended.
> 
> I'd also support moving it from deprecated => extended if someone from
> the community had an active interest in maintaining the module - regardless
> of whether or not the functionality could be replaced entirely by
> cdr_adaptive_odbc.  That way, as bugs are filed in JIRA against cdr_mysql,
> there's an actual person to assign them to and issue reporters have someone
> they can work with.  To date, no one from the community has expressed
> a desire to maintain the MySQL modules.
> 
If there is a bug that hits someone hard, there will be money put up to fix it.
I don't see that we have community maintainers for all the extended support modules either.

I don't see the value in the extra layer that ODBC provides. Complexity is scary.

Let's move it to extended and if we have a bug that makes it impossible to use, and no one
steps forward to fix it, then we propably have to re-evaluate.

I have cdr_mysql in production in many sites without issues, so I haven't been forced to work with it.
I can't accept any responsibility without funding for it, and I'm propably not the right developer for it either.
Tilghman is the one that I would pay to fix issues, since he has been doing the most recent work in
it. But he is like me, for pay and possibly not in a situation where he can accept without funding either.

So having one person tagged for each and every module seems to be a requirement that just doesn't work in this economical climate :-)

/O