Hi, I actually thought the maven item as odd as well. MRUnit deploys to the staging repository (See "Deploy to Nexus Staging Repository" http://mrunit.apache.org/pmc/how_to_release.html).
The documentation will be updated, I believe these can verified locally by using mvn site. Actually I have just looked at version I generated earlier today and there are some updates needed. Brock On Tue, Nov 13, 2012 at 3:29 PM, Ralph Goers <[email protected]> wrote: > How can I verify the Maven artifacts? It really is a problem to deploy them > after the vote since the can't be verified. > > What web site updates will be made? How can we verify those? > > Ralph > > On Nov 13, 2012, at 8:39 AM, Brock Noland wrote: > >> This is the second release for Apache Flume as a top-level project, >> version 1.3.0. We are voting on release candidate rc2. >> >> *** Please cast your vote within the next 72 hours *** >> >> The list of fixed issues: >> http://s.apache.org/A9x >> >> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1) >> for the source and binary artifacts can be found at: >> http://people.apache.org/~brock/flume-1.3.0-rc2/ >> >> The tag to be voted on: >> http://s.apache.org/aVa >> >> The KEYS file can be found here: >> https://dist.apache.org/repos/dist/release/flume/KEYS > -- Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
