...so says git. 20K sounds like a lot, but it felt like 30K edits ;) These changes were almost exclusively to sipXconfig and sipXsupervisor. In fact sipXsupervisor as you knew it, is completely gone. So you can be rest assured the bugs in the rest of the sipXecs components have been kept in tact. This should only affect the stability of the management of the system.
Maybe it's worth mentioning why these changes were made. The stability of sipXconfig and sipXsupervisor in production was mixed, varying from quite stable to unusable especially in large or clustered environments. No matter though, because the implementation of the underlying source code was not maintainable in every situation (IMHO anyway). That is no longer the case I'm glad to say (also IMHO)! The new platform is in place and a decent percentage of code has been ported to the new platform, but not everything has. I've recruited George, Cristi, Laurentiu and Mircea to assist in helping me fix broken features in 0.0.4.5.2 over the next 2 days. We'll be in the IRC on freenode in room #sipx coordinating the effort. We'll start around 4:30 AM EST each day until we crash. Folks are free to join, but we won't have a lot of time to explain things. We'd love help in the effort, but you may be on you own as far as getting setup to keep my guys focused on the main objective of getting 0.0.4.5.2 in order. You may want to leave a IRC window open if just to see the effort unfold. -- Join me to talk about sipXecs and the upcoming version 4.6 at CoLab @ CSU March (5th & 6th). http://www.sipfoundry.org/sipx-colab Hack with me on at the CoLab Hackfest. http://wiki.sipfoundry.org/display/sipXecs/2012+sipX-CoLab+Hackfest _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
