I see a number of NOTICE files in the source artifact. e.g. ./distribution/src/main/resources-hadoop1/notices/jetty-6.1.26.jar.NOTICE
I don't believe you should be including these given the artifact doesn't include those jars. I'm not sure what to make of this... would be good to add header boilerplate to Blur.html and index.html files. Otw things looked pretty good. Your git tag should probably be 'release-0.2.2-incubating-rc1" and not "release-0.2.2-incubating", given it's not approved yet (most projects use release-0.2.2-incubating-rc1 then add the release-0.2.2-incubating tag once the release is approved). This is a nit (not a release blocker) but your notice/copyright files are still 2013, should be updated to include 2014. Patrick On Tue, May 6, 2014 at 9:09 AM, Aaron McCurry <[email protected]> wrote: > This is the first release candidate for Apache Blur, version > 0.2.2-incubating. > > It fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325596&styleName=Html&projectId=12313721 > > *** Please download, test and vote by [3 working days after sending]. > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.2-incubating/ > > The tag to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=tag;h=f188e31dc57343670c001e26b767e29cec5117a0 > > Blur's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.2-incubating/KEYS
