I think we should stick with fixing bugs as found (even if that process spills into 3.5.2).  The current tests do a good job of making sure the basic functionality is in place and there has been use in the field.  Also, you've already done a good job fixing a few of the most egregious bugs.

Likewise should have an aversion to temporary APIs like _collections and to API changes between micro releases.  In general, this strategy is likely to cause more pain than it alleviates.  So, put me down for -1 on this one.