Hi all, With the qutecom 3.0 branch now published, we need to ask the question: what next?
The roadmap on the wiki: http://trac.qutecom.org/wiki/Roadmap dates from 2008 and desperately needs updating. The "roadmap" page (listing milestones & their due dates): http://trac.qutecom.org/roadmap has already been clearned up quite a bit - but we still have a 2.2 RC milestone up there, as well as the 2.3 release which, at this stage, will not happen, by the looks of it, because the move to Verona is one of the big features in the 3.0 milestone, and that is now underway. So - I think we need to start thinking about what bugs we want to get fixed in the near term before we start releasing betas for 3.0, and what our release criteria for 3.0 will be. It's worth including a small number of new user-visible features in the 3.0 roadmap, I think, but I'd suggest that the bigger goals for 3.0 are quality, the website, and restoring some features we've temporarily lost in the move to Verona. First up, what have we gained in the move? What new features are enabled by the move to Verona, and what improvements does it bring in video & audio quality? Then, what do we want to fix/stabilise before calling QuteCom 3.0? And what stuff needs to be done around the project (site, docs, services)? And what should our top priority features be? Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
