On 11/22/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
In order to use the release plugin, I have to decide to go for it, and call a particular source tree releasable. This may sound trivial, but it isn't. How do I decide that?
We've been struggling with the same issue inside Apache, where our policies require a vote on the actual artifacts that will be released. I haven't seen anything recently, but last month we had a discussion about changing the release process to include a "staging" or "proposal" phase. So it would be release:prepare, release:propose, then either release:accept or release:clean In between propose and accept is when your QA department would do their work... and if accepted, the exact artifacts they've tested will be promoted to the release repository. Here's the thread: http://www.nabble.com/Maven-and-the-Apache-processes...-t2430753s177.html#a6800959 -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
