Hi all, I'm proud to announce that from now on we will use releases in our development model. This means that there will be "stable" branches for the code which is considered working well and these branches will only receive fixes for accidental bugs, discovered after they were branched off. No new features will be introduced into stable release branches. "main" branch will be the main place for active development and the place for new features to appear. We still will try to keep it in a good shape - compiling and working, but there may be transient periods of breakage.
As a first step towards this scheme of development we've created sipXtapi-3.2 branch which contains code, previously located in main branch. You can access it for check out here: http://scm.sipfoundry.org/rep/sipX/branches/sipXtapi-3.2/ and with ViewVC here: http://scm.sipfoundry.org/viewvc/sipX/branches/sipXtapi-3.2/ As a second step, I'm going to check in a big bunch of changes regarding multicast support and some other nice features to the main branch. It won't build until I finish checking in these changes, so don't complain about this. I'll send a notice with a list of added and planned features when it is done. In short - if you're happy with your current set of features, stay on sipXtapi-3.2 branch. And if you want to test our new features - wait a few days and update your working copy! Oh, and, sure, main branch is now marked as 3.3. We're planning to use usual scheme where stable releases are marked with even version numbers and unstable ones with odd version numbers. -- Regards, Alexander Chemeris. 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/
