Staging to repository.apache.org allows folks (esp those using maven/ivy) to test the maven jars prior to the release. It's a pretty standard part of the process for most projects these days. Say you are HBase and you want to try out the proposed ZooKeeper release and give us feedback. The HBase build pulls from the maven repo in order to access the dependencies (there are other ways, but staging is a good way to do it). I'm hopeful that e.g. Bigtop will be able to help us test the release via this mechanism.
If we weren't to do this, and the release was approved and then later an issue found (once the artifacts were published as in your original description) there would be no way to rectify the issue other than doing yet another release. Staging also allows us to verify the maven deployment itself, say something were missing or a file corrupt, etc... Patrick On Wed, Feb 19, 2014 at 3:29 PM, Flavio Junqueira <[email protected]> wrote: > I think this is a question for phunt, but if anyone else knows the answer, > that's good too. Why do I need to stage the release artifacts on Apache Nexus > before calling a vote? There is the scary thing of publishing it by mistake > and not being able to pull it, so I was wondering why we don't upload the > artifacts once the vote passes. Does it make any difference? > > -Flavio > >
