Add voting to release process

Rod Widdowson rdw at steadingsoftware.com
Tue Jan 27 04:53:28 EST 2015


> 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.

> Yes, I just think the value of stable links from outside the wiki (such as
> in the list archive) outweighs the rest.

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.  

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.




More information about the dev mailing list