[asterisk-dev] Removing res_jabber, chan_gtalk, chan_jingle?

[Paul Belanger]

On 12-08-16 09:28 AM, Russell Bryant wrote:
> On Thu, Aug 16, 2012 at 9:20 AM, Matthew  Jordan <mjordan at digium.com> wrote:
>>
>> ----- Original Message -----
>>> From: "Russell Bryant" <russell at russellbryant.net>
>>> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
>>> Sent: Thursday, August 16, 2012 7:31:04 AM
>>> Subject: [asterisk-dev] Removing res_jabber, chan_gtalk, chan_jingle?
>>>
>>> Greetings,
>>>
>>> I noticed that res_jabber, chan_gtalk, and chan_jingle are still in
>>> Asterisk 11 and trunk.  Now that we have chan_motif and res_xmpp,
>>> should the old modules be removed?  It seems to me that they should.
>>> If not, why not?
>>>
>>
>> Probably just to err on the side of caution.  In the case of res_jabber,
>> it probably could be marked as deprecated, as res_xmpp is a drop in
>> replacement for it.  I'd still prefer to keep it in Asterisk 11 to ease
>> the upgrade burden on people.
>>
>> Its arguable that chan_motif is not a drop in replacement for both
>> chan_jingle and chan_gtalk.  Keeping them 'extended' for a release
>> and then reevaluating the status of those channel drivers for Asterisk 12
>> seems reasonable.
>
> Fair enough.  I'm not sure of the current status of chan_jingle and
> chan_gtalk ... if they are known to be broken, you may be doing users
> a favor by removing them now to avoid confusion about what they should
> be trying to use.
>
If they are broken, remove them.  Especially if we don't expect to fix 
them.  We already have enough people complaining they don't work.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger