hi, On Tue, 10 Oct 2006, Hadley Rich wrote:
> On Saturday 07 October 2006 20:07, Derek Smithies wrote: > > If you have a problem with your asterisk install - it crashes etc, or does > > not interoperate with your sip phone, you will (most probably) be told to > > update your astersk install, and get the latest CVS code. This is fine for > > those 1-2 user sites, but hard to justify for a 150 seat operation. Will > > the upgrade to the new CVS code break other things? In my view, it > > probably will - it is CVS level code. > > This is a problem. In reality, it's the same way for many (most?) open source > projects, the difference being those other projects aren't running your > companies phone system. Yes, and this is one more sign to indicate the "overall level of maturity" for a project. Signs of maturity: *Do they do regular (monthly or so) releases, where there is extensive testing before each release? Are releases associated with sub releases, because of bugs found in a release ? *Code documentation - is there an extensive online html documentation of the methods in the class, as generated by doxygen (or some other tool) *Do they encourage regular people to use the CVS/SVN/whatever code, or are users directed to release code? Repositary code (between releases) can only be regarded as "bleeding edge", and not suitable for installs. *Do they behave like "frat boys" on the public lists and IRCs. Other ideas on "signs of maturity" ? My impression from the meetings in Europe was that most installers had their own personal branch of asterisk, which they maintained. I do not know what NZ * installers have. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/
