Given that we do not have plenty of developer time around, we should focus *development* time on git master / 2.4 - and that includes adding testing frameworks.
+1. We should focus on doing what it takes to (finally) get 2.4 out of the door. Fairly soon afterwards we can stop worrying about 2.3 and the rather large incompatibilities between release/2.3 and master branch.
Post-2.4 we should start releasing major releases more often and with fewer features, so that the stable branch is not _that_ old when the next major release is made. That way the "release" and "master" branches do not diverge too much, and there is less need for cherry-picking patches and separately testing patching on the "release" branch. An added benefit is that more people will be using more recent code.
-- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
