As some of you probably noticed Scott created 4.0 branch. I just wanted to clarify some details pertaining to sipXconfig development.
sipXconfig on 4.0 is not "stable" yet, but it's getting there rather quickly. I would like to make sure people can safely upgrade from 3.10 before declaring it stable. There is now about 20 issues to be fixed for 4.0. But there is only 2 or 3 that are really Blockers (and I'll try to make sure that they are marked as such in JIRA). Kevin and I will continue to look after 4.0 branch: meaning all changes to sipXconfig have to have our blessing. At some point we will appoint a person responsible for stable branch who will take over that role. Do not worry about merging sipXconfig changes to mainline for now. I'll be doing this on regular bases making sure that svnmerge properties get updated properly. In parallel with getting 4.0 to stable we need to think about what's next. We already have a huge 4.2 improvement list, I have some ideas about how to implement many things that people were asking about. And I am sure that many sipXconfig contributors and users have their favourite causes and ideas. Now is the time to start discussions on the list, review the JIRA issues that you opened, re-engage with the project. I know it's been a long wait: I sincerely hope that we switch back to a more reasonable "fixed release date" from current "fixed release content" model with sipXecs. It's not entirely up to me but I'll try to lobby for that. I'd like us to release sipXecs every 6 months (if not more often): so that people can try new features without using unstable builds. Thanks, Damian _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
