> OK, let's put this is a more palatable perspective then. What
> outstanding issues are yet to be resolved before 1.32b is ready for a
> release version? I am less interested in a date than understanding what
> issues are still to be resolved and therefore holding things up.
> Perhaps knowing that would allow me / you / someone / anyone to assist
> in moving forward.
It is a little slow on embedded and older hardware. It has some
unpredictable behavior in some features. What it really needs is a lot
of use, bug reporting and patching. What you can do is try it, and test
it. However, you need to be able to do real bug reporting and fixing,
not just "feature X is broke!" :)