Testing releases

[Dan Haywood <da...@haywood-associates.co.uk>]

Just moved this from the VOTE thread so that thread it doesn't get too
polluted...


> Rob wrote:
> PS is it worth making your release experiment available so I can try out
releasing a component. Or are  you close enough that it will be quicker
(from both sides) to wait for the real release.


I'll put out an experimental release of core tonight or tomorrow (up to and
including deploying a release to the Nexus staging repo [1]) and I'm also
going to do see if I can do an experimental release of wicket and jdo.

Just a heads-up: in order to do a release, you need to have a signed key
that has been signed by other committers.  The process to create the key,
if you don't have one, is documented on the site [2].  To have it signed by
other committers (a prereq for any Apache release)  requires a face-to-face
verification [3].  Kevin and I both have our keys counter signed, so either
of us can extend the "web of trust" to your key.  Until then, though,
either Kevin or I will need to push out releases on your behalf.


[1] http://isis.apache.org/contributors/release-process.html
[2] http://isis.apache.org/contributors/key-generation.html
[3] http://www.apache.org/dev/release-signing.html#key-signing-party