Damian Krzeminski ha scritto: > 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. > I totally agree with Damian in this matter. The major objection I see in this project, in respect of many other successful open source projects, it's total uncertainty of release date. I'm sorry to say this, because I appreciate the great work you do guys, but I've never seen (and I'm here since 3.0) an estimated release date in the roadmap actually being respected (maybe 3.4 that was a sort of surprise release). Right now 4.0 roadmap release says end of March, but it was end of 2008 some time ago ... From an user point of view I do not expect all new features to become stable magically in a short time. Some major improvements need a great effort for you guys but I believe they need to be worked out separately until they are stable enough to be introduced in the main tree. I've seen the main build passing from very stable to very unstable. This is extremely negative cause force you to work out something instead of saying simply "that new feature won't make it for the release date let's move it to the next one". What you start in main needs to be completed if not working and of course you are forced to push the release date. I'm not against that some feature could be marked ad experimental in a stable release. I was following sipxbridge since it first appeared and it was working fine with 3.10 even without a specific sipxconfig user interface. It's a component that will need a lot of testing cause it nature to be interoperable with a large array of ITSP. I think that a deep testing of this component (with the wider range possibile of ITSP) will happen only when it will be in a stable release. Again from a user point of view sipxbridge could have been released in a maybe 3.12 long time ago. I'm sure now it is greatly improved but it had to wait for other unrelated new features to just come to our machines. Just taking inspiration from other successful open-source projects fix a six month release date with the appropriate new feature freeze date, and beta date. All developers and users, in my opinion of course, will take great advantage of this.
Alberto _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
