Add voting to release process

[Cantor, Scott]

> > My plan for documenting post-3.0 properties and beans was to use
> > superscripts to notate anything in the tables that was newer.
> 
> Pretty much like the SP.  Works for me.

I'm hoping the superscripts make it less intrusive.

> I don't think that there is a "rest" to outweigh.  I don't see that there is
> any advantage in a new space.  Perhaps there might be if confluence
> supported source control and merging of context forwards and backwards.
> But in that case we'd just cut a branch off the TRUNK documentation for the
> previous release every time we did a release.

The idea was that it was too confusing to figure out what was supported by which version. I didn't necessarily buy it, but that was the thought.

> Which I suppose asks the question, if there is any value in per release
> spaces why don't we clone IDP30 into IDP3'n'_RELEASE when we do the
> release for 'n+1'?  But this would still be in addition to the "new since 3.1"
> annotations.

The main problem with that is the constant incomplete state of the docs. If we ever had something we called "done", then it might work, but until then we just end up cloning incomplete information.

-- Scott