Thomas Kenyon wrote: > MM _ wrote: >> Hey guys, >> >> I think we should get our CallWeaver page back on wikipedia, but probably >> wait till >> 1.2.0 is released so we dont run into the same problems. >> >> There's only 9 open tickets (one is mine, I know), does anyone know what the >> holdup >> is and a rough ETA of having them closed? >> > I must confess, one of the things I am really enjoying so far with > callweaver is the way releases appear to be being scheduled. > > I've lost count of the number of times I've upgraded my asterisk test > suite at home to the latest release, then a few days later at a call > centre, only to find things stop working at the call centre (home can > hardly be exactly the same conditions). > > Having a release policy of picking a moment and then having whatever the > current cvs trunk renamed to the current release build only to find that > there are more things broken than fixed is starting to wear a bit thin. > > To all concerned, well done and keep up the good work.
Greetings, I thought I would chime in as a core Asterisk developer and provide some insight in to how the the process actually works for us and what obstacles we face. Perhaps you guys can take it into consideration in case you experience the same thing down the road. We do all current active development in trunk, developers usually create a branch off of it and then merge their work back in. As time goes on we freeze trunk in various stages. API changes, feature changes, etc and then branch it off so it becomes the current release branch. This release branch becomes bug fixes only. We then try to do our own testing and ask that the community tests. Some time later when we are comfortable we release a first version and so on. Ultimately though we can't test every situation that an individual is going to run into it, and thus bugs crop up. Are there bugs we introduce? Sure, but we are only human. Do we release often? Sure, due to critical bug fixes and critical security fixes. Thomas: I would be curious to know from an outside perspective what you think of it and how Asterisk is handled. Would you care to have a conversation off list? Joshua Colp "file" _______________________________________________ Callweaver-dev mailing list Callweaver-dev@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-dev
