Re: [Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-20 Thread Aryanto Rachmad
: Asterisk Development Team [EMAIL PROTECTED] To: Asterisk Developers Mailing List asterisk-dev@lists.digium.com Sent: Thursday, January 19, 2006 1:05 AM Subject: [Asterisk-Dev] Asterisk 1.2.2 Released! Greetings everyone! The 1.2.2 versions of Asterisk, Zaptel, and Libpri have now been released

Re: [Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-20 Thread Kevin P. Fleming
Aryanto Rachmad wrote: I have a question which probably sounds silly. I am using Asterisk SVN-branch-1.2-r8140 built. To be honest I am still confused with this SVN things. The main reason I use it is that I think I can get the bugs fixed by updating it regularly, which I previously could

Re: [Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-20 Thread John covici
What about using trunk -- will that get me 1.2.2 or netsec of both? on Friday 01/20/2006 Kevin P. Fleming([EMAIL PROTECTED]) wrote Aryanto Rachmad wrote: I have a question which probably sounds silly. I am using Asterisk SVN-branch-1.2-r8140 built. To be honest I am still

Re: [Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-20 Thread Russell Bryant
Tzafrir Cohen wrote: The following assertions are based on my own knowldge and are hopefully close to correct. Feel free to comment: 1. The version of Asterisk and the version of libpri must match. The API should never change between minor releases. 1.2.X of Asterisk and 1.2.X of libpri

[Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-18 Thread Asterisk Development Team
Greetings everyone! The 1.2.2 versions of Asterisk, Zaptel, and Libpri have now been released. The source tarballs are available for download on ftp.digium.com. For details about what has changed, see the ChangeLog for Asterisk, Zaptel, or Libpri. We are also excited to announce the release of

Re: [Asterisk-Dev] Asterisk 1.2.2 Released!

2006-01-18 Thread Steven
On Wed, 2006-01-18 at 18:05 -0600, Asterisk Development Team wrote: Asterisk-addons and Asterisk-sounds will remain at version 1.2.1. Previously, all packages were updated to reflect a matching version number, even if no changes have been made. From now on, releases will only be made when