cpg1.3.1 and cpg1.3.2 have only been bugfixes, no new versions went into it - it would have required all translators to rework their translation, which is way too much effort. The next release that has genuinely new features will be cpg1.4.0.
The mantra of open source development is "release early, release often" - we're trying to reduce the time between the releases of new versions by introducing a language fallback - this way, less time will pass between cpg1.3.x and cpg1.4.x than between cpg1.2.x and cpg1.3.x (but maybe this is just wishfull thinking). We also plan to release alphas to a reduced number (non-publicly) of testers, so we can start sooner to start bug-fixing. The problem is: only if a version gets released to a broader audience, all (or at least most) hidden bugs are being discovered, but people don't understand the difference between an anlpha or beta release and a stable one. If we release betas to the public, our support board gets flooded with newbies asking questions on one and the same bug, although extra large fonts say on all beta versions "don't use on production servers, only for testing".
If you need additional features, and you need them fast, do as I suggested and check out the cvs - just be sure you can live with bugs and the fact that there can be no support for code that is under development.
Joachim