Hi all, The 2.1 release is starting to make some waves, and now is the time to look forward to the next release.
The big change which is already underway is the migration to the CoIP manager, the all-singing all-dancing modular architecture which Philippe and Tanguy have been working on for the past months. This change alone will justify the version number 3.0. Aside from this change, which will inevitably end up being a key part of the next release, I am looking for feedback on the features that we should be focussing on for this release cycle. Features don't necessarily mean new functionality - you might consider that we should focus on the usability of a particular part of the program, or the stability of a particular module. I don't want to put words in your mouth. What I do want is your ideas for things which you think should be proirities for this release cycle. I will also be looking to get people involved - if there is a pet feature that you are particularly interested in, then a patch, or even a decent spec and mock-up, will be welcome contributions. Based on the list of ideas I get from the community, and from companies working with OpenWengo, I will be publishing a first draft of a roadmap for the 3.0 release (and the release cycle beyond 3.0) during the next two weeks. Thank you very much! Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
