On 23 Dec 2013 18:32, "Matt Benson" <gudnabr...@gmail.com> wrote:
>
> Bene pointed out to me that he did build w/ Java 7; of course the target
> setting in the POM is the reason the classfiles are Java 6 compatible,
> which is the important thing in any case.

Presumably that means the Javadocs have a Java 7 style? Is that a problem
or do we produce the website Javadocs in a different process?

Duncan

>
> Matt
>
>
> On Mon, Dec 23, 2013 at 11:00 AM, Matt Benson <gudnabr...@gmail.com>
wrote:
>
> > - RAT report looks okay.
> > - I successfully build the contents of the source artifacts with both
Java
> > 6 and Java 7
> > - I successfully build the contents of the tag
> > - britter code signing key is in
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> > - All sigs and hashes check out
> > - Binary jars appear to have been built using Java 6
> > - All LICENSE and NOTICE files appear to be where they should
> >
> > +1 to release from me.
> >
> > Matt
> >
> >
> > On Sun, Dec 22, 2013 at 5:11 AM, Benedikt Ritter <brit...@apache.org
>wrote:
> >
> >> Hello All,
> >>
> >> We have fixed quite a few bugs and added some significant enhancements
> >> since Commons Lang 3.1 was released, so I would like to release Commons
> >> Lang 3.2.
> >>
> >> Commons Lang 3.2 RC1 is available for review here:
> >>     https://dist.apache.org/repos/dist/dev/commons/lang/ (svn revision
> >> 3964)
> >>
> >>   Maven artifacts are here:
> >>
> >>
> >>
https://repository.apache.org/content/repositories/orgapachecommons-014/org/apache/commons/commons-lang3/3.2/
> >>
> >>   Details of changes since 3.1 are in the release notes:
> >>
https://dist.apache.org/repos/dist/dev/commons/lang/RELEASE-NOTES.txt
> >>
> >>
> >>
http://people.apache.org/~britter/commons-lang3/3.2-RC1/site/changes-report.html
> >>
> >> The tag is here:
> >>
> >>
http://svn.apache.org/repos/asf/commons/proper/lang/tags/LANG_3_2_RC1/(svn
> >> 1552978)
> >>
> >> Site:
> >>   http://people.apache.org/~britter/commons-lang3/3.2-RC1/site/
> >>   (note some *relative* links are broken and the 1.2 directories are
not
> >> yet created - these will be OK once the site is deployed.
> >>   Also note, that PMD shows a lot of warnings due to useless
parenthesis.
> >> We have decided to leave these in the code for readability.
> >>   Findbugs has a few warnings, none of which we consider to be
dangerous,
> >> but as always: patches are welcome ;-)
> >>
> >> Clirr Report (compared to 3.1):
> >>
> >>
> >>
http://people.apache.org/~britter/commons-lang3/3.2-RC1/site/clirr-report.html
> >>   (note that the Clirr report show 3 errors. This changes are
considered
> >> to
> >> be save for client code. More Information about this can be found in
the
> >> release notes)
> >>
> >> RAT Report:
> >>
> >>
> >>
http://people.apache.org/~britter/commons-lang3/3.2-RC1/site/rat-report.html
> >>
> >> KEYS:
> >>   http://www.apache.org/dist/commons/KEYS
> >>
> >>   Please review the release candidate and vote.
> >>   This vote will close no sooner that 72 hours from now, i.e. after
> >> December 25 2013 at 12:30 CET
> >>
> >>   [ ] +1 Release these artifacts
> >>   [ ] +0 OK, but...
> >>   [ ] -0 OK, but really should fix...
> >>   [ ] -1 I oppose this release because...
> >>
> >>   Thanks!
> >>
> >>   Benedikt
> >>
> >> --
> >> http://people.apache.org/~britter/
> >> http://www.systemoutprintln.de/
> >> http://twitter.com/BenediktRitter
> >> http://github.com/britter
> >>
> >
> >

Reply via email to