public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Update asterisk addon
Date: Wed, 09 Jul 2014 20:53:51 +0200	[thread overview]
Message-ID: <1404932031.16965.10.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <74fc696b793d57d83f7456ac989d093b@mx6-sysproserver.de>

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

Hey,

thanks for sending this in. I had a quick look at the changes and some
remarks and questions that I would like to ask.

On Mon, 2014-07-07 at 09:27 +0200, Dirk Wagner wrote:
> Hi,
> 
> updating the asterisk addon is completed and ready for reviewing/testing 
> tree.
> 
> Here the changes from previous version:
> 
> * update to LTS realease 11.10.2

It is certainly a good idea to stick with a LTS version.

> * full TLS/SRTP support via libsrtp

This is a great feature. Although I would suggest to build the library
in a seperate lfs/ file.

> * logrotate support
> * removed webif
> * removed support and dependencies to ffmpeg, snmp

Therefore we will be able to put asterisk into the main repository and
out of the testing repository.

> * removed chan_capi support (this will maybe released as a seperate 
> addon in the future)

I guess that there are no users who need this feature any more. We
should certainly make a big announcement that people will be aware of
this change prior to installing the update.

> Due to build issues I updated the LCR addon to 20140403, but this is 
> completely untested due to lack of hardware.

Arne will help us testing that.

> Plz pull from
> http://git.ipfire.org/?p=people/glotzi/ipfire-2.x.git;a=shortlog;h=refs/heads/asterisk-update
> 
> The branch also contain a bugfix for missing include in logrotate.conf:
> http://git.ipfire.org/?p=people/glotzi/ipfire-2.x.git;a=commit;h=f5a99cd4e2c73586930119bf5c255e1ba2e452c4

I will pull in this commit before merging the rest. It is independent
and we should ship it with core update 80.

With all the rest, please respond to my annotations above and we will
see when we are ready for the merge.

-Michael

> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development


      reply	other threads:[~2014-07-09 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  7:27 Dirk Wagner
2014-07-09 18:53 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1404932031.16965.10.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox