Preparation for Release

[Patricia Shanahan]

This is probably unnecessary, but I wanted to make sure everyone 
understands the requirements for casting binding votes in favor of a 
release. See http://www.apache.org/legal/release-policy


In particular "Before casting +1 binding votes, individuals are REQUIRED 
to download all signed source code packages onto their own hardware, 
verify that they meet all requirements of ASF policy on releases as 
described below, validate all cryptographic signatures, compile as 
provided, and test the result on their own platform."


I am preparing for this by working on being able to build and test River 
on one of my computers.


Patricia

Re: RAT reports

[Peter]

Yes, all policy files and scripts have found their way into the project either 
by the original contribution, commits or patches on jira, all of which required 
agreement to license each contribution under the al2 license.  Many, especially 
policy files in the qa suite, didn't have license headers, I guess the original 
focus was on java code.

In this case, when no license headers exist, we are safe to prepend al2 license 
headers.

Anything else, under an al2 compatible license,  has license headers, we've 
always been pedantic about that, eg: some ASM code, which is used by classdep.  
These licenses are also noted in a license text file on the build root 
directory.

Thanks for getting this sorted.

Regards,

Peter.

Sent from my Samsung device.
  Include original message
 Original message 
From: Patricia Shanahan 
Sent: 08/12/2015 10:39:50 am
To: dev@river.apache.org
Subject: Re: RAT reports

Ignoring the manifest files, which arguably do not involve enough  
creativity to be the subject of copyright etc., do you know the origins  
of any of the other files? The real work is determining their copyright  
and license status. 

On 12/6/2015 8:42 PM, Peter wrote: 
> I don't think it's possible, I can't find any examples. 
> 
> Peter. 
> 
> Sent from my Samsung device. 
>Include original message 
>  Original message  
> From: Patricia Shanahan  
> Sent: 07/12/2015 02:30:16 pm 
> To: dev@river.apache.org 
> Subject: Re: RAT reports 
> 
> Does anyone how one puts a license header in a manifest (.mf) file? 
> 
> Patricia 
> 
> On 12/5/2015 8:12 PM, Peter wrote: 
>>   Thanks Patricia. 
>> 
>>   Looks like there's a number of policy files and scripts that need header 
>>files. 
>> 
>>   Anyone have time to write a script to parse the Rat reports and prepend 
>>license headers? 
>> 
>>   I reconfigured the integration tests to run against trunk.  I noticed 
>>there are about 7 test failures in the unit tests, although none look 
>>particularly concerning, I'll have a better look later to make sure. 
>> 
>>   It would be nice if the jtreg tests ran on hudson, unfortunately they 
>>don't presently; the jtreg platform library isn't installed correctly. 
>> 
>>   I have run the jtreg tests locally and 132 pass on linux as expected.  
>>There are some remaining Windows path issues, so not all pass on that 
>>platform. 
>> 
>>   I'm about to generate and update the release notes.  I'd also like to 
>>include a link to Dennis' examples on github. 
>> 
>>   Next we need to get our pgp encryption keys ready.  My old key expired so 
>>I'll have to generate a new one. 
>> 
>>   We're almost there, any assistance will be most appreciated. 
>> 
>>   Regards, 
>> 
>>   Peter. 
>> 
>>   Sent from my Samsung device 
>>  Include original message 
>>    Original message  
>>   From: Patricia Shanahan  
>>   Sent: 06/12/2015 12:59:41 pm 
>>   To: dev@river.apache.org 
>>   Subject: RAT reports 
>> 
>>   RAT is still Java - it is just packaged as a .bin.zip. 
>> 
>>   I was not able to run the script directly in Cygwin, but was able to get 
>>   the reports by pasting the guts of it into a bash window. I attach the 
>>   resulting reports, and hope the mail system will let them through. 
>> 
>> 
> 
>