3.2.4's been out for a *long* time, we more or less dropped our effort on it.
You've probahly read some of the criticisms of 4.x, i.e. the fact that in many ways it's not complete or ready for prime time. That kind of messed us up as we were pumped to start porting soon after it was released then were somewhat deflated by the news that it (ummm) sucks in some (not all!) ways.
Keep in mind that the group actively involved in helping out with tasks was *far* smaller as recently as six months ago. We've now got a lot more volunteers, as well as people using the code, reporting bugs and often fixes.
What a luxury!
The current plan is to release at least two or three more 3.2.* updates, say every three months or so. 3.2.5 looks to be very solid, but if need be we could release a 3.2.6 in more like a couple of months. These will strictly be maintenance releases. Roberto's setting up a "contrib" mechanism for user add-ons (like the back-port of the db api). The SDM will be enhanced with Pascal's updates so we can tie patches submitted to the SDM and applied to bug reports.
Should help a lot.
Jonathan is working on 3.2.5 RPMs this weekend so it looks like Roberto will be ready to announce on Sunday? Monday? Very soon.
