< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Calling all devels: Getting release notes ready, other release work.


Hi Byron,

thanks for pushing for the 1.0 release!

Here's the tiny list of my contributions:

New Features

- STUN client support (in UdpTransport class)
- Added capability for adding a MessageDecorator through a dum profile


Fixes and minor changes

- made codec comparison case insensitive (findFirstMatchingCodec function)
- modified stunTest to use nonblocking socket and selectable timeout
- Added some missing closesocket calls to the rutil\STUN functions
- removed the static "done" check in Security::Initialize(), it caused a bug 
when the object was instantiated a second time
- Corrected the Codec constructor for telephone-event and frf-dialed-event 
constants. A payload type of 8000 was used. (Not wrong but usually 101 is used. 
8000 rather is the bandwidth)
- Added two more codec constants. (G723 and GSM)
- removed the bogus sleep stuff from stunSendTest


Best regards,

Matthias Moetje
______________________________________________

TERASENS GmbH       Phone:  +49.89.143370-0
Augustenstraße 24   Fax:    +49.89.143370-22
80333 Munich        e-mail: info@xxxxxxxxxxxx
GERMANY             Web:    www.terasens.com
______________________________________________ 

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Byron Campen
> Sent: Monday, August 21, 2006 5:00 PM
> To: resiprocate-devel
> Subject: [reSIProcate] Calling all devels: Getting release 
> notes ready,other release work.
> 
>       I think that the easiest way to get thorough/accurate 
> release notes out rapidly is have everyone go through their 
> commits since the last release, and summarize what they have 
> done. Everyone who is willing to devote some time to doing 
> this, please reply within the next two days. If anyone wants 
> to pick up for additional developers, let me know who. I will 
> probably be the one who goes through the remainder, so please 
> help out if you have time. I would like to shoot for having 
> this done before Friday.
> 
>       We have additional issues to discuss, such as:
> -Do we want to have any sort of documentation push?
> -Naming-scheme for this release (and following releases) 
> -Scheduling the final 1.0 release (two weeks from now?) 
> -Anything else anyone can think of (recall that I have never 
> done this sort of thing before; _please_ chime in!)
> 
> Best regards,
> Byron Campen
> 
>