Hi all, It seems pretty clear that there's no real demand for a 2.3 release - especially since the trunk is now moved to Verona, and it would be nice to concentrate efforts on stabilising this branch and adding features there.
So I would like to start moving tickets off the 2.2RC4 and 2.3 milestones, and either moving them to the 3.0 milestone (if they still apply, and if they are considered blockers for the 3.0 release) or moving them to no milestone (if we aren't in a position to say straight away whether they'll be done for 3.0). I'd really like to get some help for this - it's a straightforward task, but it'll definitely need more hands to get it done quickly. I'd like to see a comment saying whether the bug still applies to the trunk post-Verona merge, and whether it should be on the 3.0 milestone. Bugs which don't apply to the trunk pose something of a problem - I'm tending towards closing them WONTFIX, since if they only apply to the 2.3 branch, it's unlikely they'll ever get fixed. Can I get some feedback on this plan, please? Do people think that it would be useful to make one final release on the 2.3 branch, and call it 2.3.0? It seems like all the fixes in the 2.3 branch are also in the trunk, so I'm not sure I see the value. Cheers, Dave. -- Dave Neary Email: dne...@free.fr Jabber: nea...@gmail.com _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
