On Thu, May 21, 2009 at 4:23 AM, Henri Yandell <flame...@gmail.com> wrote: > I don't expect this to pass the first vote - they never do :) > <snip/>
Minor nit IMO is that the release plugin took out the pom license header. Dry running release:prepare will help fix the glitch. -Rahul > --- > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/collections/tags/COLLECTIONS_3_3_RC1 > > Site: > > http://people.apache.org/builds/commons/collections/3.3/RC1/site/index.html > > Binaries: > > http://people.apache.org/builds/commons/collections/3.3/RC1/staged/commons-collections/commons-collections/3.3/ > > > Clirr: http://people.apache.org/~bayard/commons-collections/diff.txt-clirr.txt > > Jardiff: > http://people.apache.org/~bayard/commons-collections/diff.txt-jardiff.html > > --- > > Currently I've noticed that the site/release notes say 'JDK 1.2' when > in fact it's 1.3 source/target from a 1.5 JDK. Also the test jar is > not deployed to the Maven repository. That can be done manually if > desired. > > I'm interested in what others find. > > Hen > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
