[Sipwitch-devel] sipwitch 1.0 release plan

[David Sugar]

I actually had this in mind somewhat since yesterday, but I decided to
execute on this more immediately.  Basically, I am branching sipwitch
into a 1.x release branch to stabilize current functionality as needed
for things like the portal project, and a (2.0) trunk for developing gfc
related features.  The key feature that held back a 1.0 release has been
completion of rtp proxy for nat.  I could push this functionality out of
the 1.0 release if it is needed to get it out, or at least get some
further minimal fixes and disable it in the default sipwitch.conf.  I
think the sdp rewrite code ultimately needs to be excavated from the
server and made into separate unit testable methods in libsipwitch.  I
think we will then also have a 1.0 release this or next weekend.

I already had split ucommon between a 4.x release branch and trunk over
the past weekend.  Trunk will be used to test and provide a single
merged ucommon with commoncpp support library as was experimentally done
in the merge branch a few months back, and this will be ucommon 5.  This
means that with ucommon 5, both ccrtp and libcppzrtp should all finally
be able to build on a single codebase derived from ucommon, and through
a complete cmake build tree.  This I think is now a high priority
effort.  I would like to see if we can get ucommon 5.0 out by the end of
the month since much of the hard work for this was initially already
done and somewhat tested in the merge branches a few months ago.

Finally switchview is going to move into and be released as/part of a
package to be called (g)taps (GNU Telephony Application Programs &
Services).  This will leave room for additional things to be added to it
in the future, too, such as switchadmin.  I think it will be ready for a
preliminary release before the end of the month also.

All comments and discussion welcome on this release plan.