sipXpbx -- This is outside of the sipXtapi project branches/sipXtapi -- This is our main development branch -- active development happens here, and it changes from day to day, sometimes hour-to-hour.
branches/sipXtapi-media-update -- A closed branch that was used when implementing video enhancements to sipXtapi - it has since been merged with the main branches/sipXtapi branch. Jaro's Experimental "branch" -- Jaroslav Libak has done a massive change to sipXtapi (just the sipXtapi portion I believe, not the stack, port, etc libs) - this is the result of his efforts. There are a number of API changes, and it is controversial, yet it does clean up quite a few bugs and memory leaks in sipXtapi. Does that help? On 7/17/07, Pedro Sanchez <[EMAIL PROTECTED]> wrote:
Hello, I'd like to have some clarification on how the source code is being managed for the sipxtapi project. The Wiki page talks about three code branches: sipXpbx main, branches/sipXtapi, and branches/sipXtapi-media-update. In another thread Jaro told me about the "experimental" branch. >From the Wiki page I get the impression that branches/sipXtapi is the branch targeted by most active developers these days. But Jaro's statement "Experimental sipXtapi is refactored, and I think should be less buggy" makes me wonder. So, for a brand new project (a prototype actually) that requires a SIP library, which sipxtapi code branch shall I use? Thanks, -- Pedro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
-- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
