Create 3.2 Branch

[Rod Widdowson]

> we can just continue on trunk and if
> we need to branch for a patch, we'll copy it from the 3.2.0 tag. So all
you need
> to do is bump the version in trunk to 3.3.0-SNAPSHOT.

It strikes me that it would be easier to put a tag in place for now.  There
are a few bugs, currently fixed against 3.2.1 which would need to be merged
forward.  Or of course we could just start the at 3.2 branch at r8019 (or
wherever).

But there is a meta discussion (which I may have missed/forgotten) whether
the next release we "expect" to ship is 3.3  or 3.2.1.  If we expect that
3.2.1 will only be for critical security fixes then we won’t be merging
anything, just fixing the bug.  If we expect to do a roll-up 3.2.1 prior to
a 3.3 then it's another matter.  I have enough nitty little bugs which
require a minor upgrade that I'd favour the former, and from the language
above it seems that you do too,

> But +1 to that. Branching is symbolic in this case.

> Here's Tom's +1.

And my +1