[Serusers] [Serdev] Release of SER 2.0 (and future 2.1)

[Greger V. Teigre]

Ok, I conclude then that final release of SER 2.0 is aimed at October 
15. That should allow us to align SER, serctl, SERWeb, rtpproxy, and 
SEMS. SER, SERWeb, and SEMS will have independent releases, and they 
will be aligned to be interoperable. SER, rtpproxy, and serctl will have 
a common release.

The release will include the new buildsystem that was tested in release 
candidate 1. The config file and features available work with sercmd, 
serctl, as well as with SERWeb. SEMS support is planned, but pending 
some patches. 

All components will be combined in a one-file download with sources for 
all components, the SIP Express Bundle.

I urge everybody with patches, bug reports, or tasks related to this 
release to prioritize those now!
g-)

Greger V. Teigre wrote:
> Guys,
> My last post concerned documentation. I suggested decoupling 
> documentation from the CVS to allow us to work independently with code 
> and docs. 
>
> I suggest we move forward on the decoupling and set a date for SER 2.0 
> release.  My suggestion is that we target October 15.  This will allow 
> people to allocate time to do the last clean-ups, bug-fixes, and patches.
>
> I also suggest that we set a release date for 2.1.  AFAIU, there is 
> already quite a lot of code that has gone into the trunk and as 2.1 is a 
> minor release and we strive for ser.cfg compatibility with 2.0, we 
> shouldn't really wait too long.
>
> I suggest mid-January 2008. How does that work for you?
> g-)
> _______________________________________________
> Serdev mailing list
> Serdev at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serdev
>
>
>