Wanted to give you the good news that we almost completed the reorganization of the SIPfoundry tracker and are now ready to drive development again out of this tracker. You might have noticed quite a few issues being merged in over the last few days and we did quite a bit of cleanup to get ready. We also properly configured the Agile plugin so that we can use this going forward to assist setting priorities.
We are still working on some of the other infrastructure components, such as the Web site, and will come back soon with some news here. Also wanted to thank everyone for the tremendous response and tangible help we received over the past few weeks. It was much appreciated and we are looking forward to intensifying the open source collaboration going forward. Let me maybe address one key question that keeps coming up: "I reported XX-???? already back in <pick your favorite month> and this is really a fundamental flaw of sipXecs but nobody has done anything about it yet". As you can see there are quite a few issues deemed 'fundamental'. Everyone has a different list of priorities, given by the specific requirements, application or deployment scenario you encounter. Especially SIP trunking and NAT traversal involving all kinds of routers and firewalls is still more art than science and different ITSPs are different. That's why we have not and cannot certify (or even fix) them all, no matter whether the problem is deemed to be on the sipXecs side or the ITSP side. The most efficient way to get the project to adopt your list of priorities is to participate. Not everyone is a programmer - what do you do in your business if you need something done that you cannot get done yourself? We are working on converging on a release this fall and as Douglas pointed out we are counting on everyone to assist with testing. --martin
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
