incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Bayer <>
Subject Re: [VOTE] Release Apache jclouds 1.6.1-incubating
Date Fri, 31 May 2013 03:18:14 GMT
NOTICE is being generated (I believe in all cases) from incubator-jclouds.git/resources/NOTICE.txt
- I think the resources/NOTICE.txt in chef may be from an earlier incarnation, but I'm not
100% sure. It does look like we are overly broad in the list of included code in NOTICE, but
I'm not sure whether we should have separate NOTICEs for each sub project or if we can just
use one that's applicable across all of them. This is my first ASF project with separate release
artifacts for source projects.

I'll fix the tarball names by hand for this RC tomorrow morning, and we'll figure out the
best way to get them automatically named correctly going forward, including any subsequent
RCs if they prove necessary for code reasons, etc.

We've been uncertain about how to handle test resources - there are a good number of test
resources which are just used for validating test output, and we'd have to have the tests
spit out the license headers as well as their real output if we had license headers in the
output comparison resources. As a result, we've excluded src/test/resources from rat checks
in the build. This may have been too broad an exclusion, but we'd like to make sure we know
what can get away with not having a license header and what can't before we change that.


On May 30, 2013, at 7:41 PM, David Nalley <> wrote:

> On Thu, May 30, 2013 at 3:44 PM, Andrew Bayer <> wrote:
>> Hello,
>> This is the first release candidate for Apache jclouds 1.6.1-incubating,
>> the first jclouds release at Apache.
>> We are calling this vote on both the IPMC and the jclouds PPMC at the same
>> time, as the code for this release has already been vetted by the jclouds
>> developers leading up to this RC.
>> It fixes the following issues:
>> *** Please download, test and vote by Sunday, June 2nd, 1pm PDT.
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>> Source and binary files:
>> Maven staging repo:
>> The tags to be voted upon:
>> - jclouds -
>> - jclouds-labs -
>> - jclouds-chef -
>> - jclouds-karaf -
>> - jclouds-cli -
>> Whirr's KEYS file containing PGP keys we use to sign the release:
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>> Please note whether you're voting as an IPMC member, a jclouds PPMC member,
>> or both. Thanks!
>> A.
> Hi Andrew:
> I've started looking at the chef bits (haven't gotten past that, yet)
> but NOTICE looks eerily familiar.  Can you tell me how NOTICE was
> generated? Jersey, for instance, is listed as being included, but I
> can't find it bundled into source of chef source tarball anywhere.
> Have you seen:
> There's also an issue with naming - chef-project does not match naming
> specified at:
> What are the LICENSE.txt and NOTICE.txt files under resources/ intended for?
> The json files in core/src/test/resources/ don't seem to have license
> headers - or at least not all of them do - one or two of them do
> contain a license header.
> --David
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message