On Apr 18, 2012, at 5:56 PM, Robbie Gemmell wrote:

> I have run Rat on the 0.16 RC2 release tar, the output can be found here:
> http://people.apache.org/~robbie/qpid/0.16/0.16rc2_rat_output.txt
> 
> There are a number of new files without licence header since the last
> release that need updated. I will update the Java related files on
> trunk tomorrow, it would be helpful if others could look over the
> output and do the same in their respect areas of choice.
> 
I can update the JCA files, actually most of them have already been updated in 
a later release. 

Regards,

Weston
> Robbie
> 
> On 11 April 2012 22:14,  <[email protected]> wrote:
>> RC2 from revision 1324655 is available here:
>> 
>>  http://people.apache.org/~jross/qpid-0.16-rc2/
>> 
>> This RC fixes the problem with embedded svn versions that Robbie raised. It
>> also has the following bug fixes:
>> 
>>  jross@nicaea qpid-0.16$ svn log -r 1309391:HEAD | fgrep QPID
>>  QPID-3937 - Back-ported fix from trunk into 0.16.
>>  QPID-3938 - Back-ported fix from trunk into 0.16
>>  QPID-3901: merge fix to 0.16 branch
>>  QPID-3900: merge fix to 0.16 branch
>>  QPID-3919
>>  QPID-3905: NullPointerException is thrown on rejecting messages whilst
>>    closing the connection
>>  QPID-3911: Fix deadlock on concurrent invocation of
>>    MessageConsumer#close() and Session#rollback() from consumer
>>    MessageListener
>> 
>> A point in passing: It helps (helps scripting like the above and git
>> mirrors) if merges to 0.16 include descriptive text on the same line as the
>> QPID- reference.  Rather than "merge fix to 0.16", it's better to copy the
>> summary from the original trunk commit.  In other words, follow Robbie's
>> example in the last two commits, :).
>> 
>> Finally, there's stirring on the list about a python build issue, and there
>> are two ruby build issues not yet on the release branch.  These may call for
>> another RC.
>> 
>> Thanks,
>> Justin
>> 
>> ---
>> 0.16 release page: https://cwiki.apache.org/qpid/016-release.html
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to