3.2.0

This is clearly my fault. I lost track of the plan. Going forward, I need to get a better handle on plans -- I've been to reactive, having discussions spread across launchpad, GitLab, IRC, and the mailing list. Here's one proposal: instead of reverting the recent merge, we could cut a release off master before the merge. That would give us a less disruptive release (at the expense of a little complexity on the release branch). Would this make everyone happy? Sent from my iPhone