As its just a maintenance release, 7 days seems a little long.  Let’s just 
leave it at ‘at least til Thurs’ and we can leave it open as long as it takes 
to get 3 ‘+1’s.  I think it would make sense to finish off this vote before we 
open the voting on ‘3.0’, but that’s up to whoever is acting as ‘3.0' release 
manager.

For what it’s worth, I’ve run the integration tests (not the jtreg tests) on a 
Raspberry pi and they pass.



Cheers,

Greg.
> On Feb 8, 2016, at 11:23 PM, Peter <j...@zeus.net.au> wrote:
> 
> We might need a little more time than 72 hours to build and run tests.  Can 
> you make the vote close Monday? That'll provide some more time for review.
> 
> Peter.
> 
> Sent from my Samsung device.
>  
>   Include original message
> ---- Original message ----
> From: Greg Trasuk <tras...@stratuscom.com>
> Sent: 09/02/2016 10:49:11 am
> To: dev@river.apache.org
> Cc: u...@river.apache.org
> Subject: Re: [Vote] Release Apache River 2.2.3
> 
> 
> +1 from me. 
> 
> Greg Trasuk 
> 
>>  On Feb 8, 2016, at 5:02 PM, Greg Trasuk <tras...@stratuscom.com> wrote: 
>>   
>>  Hello all: 
>>   
>>  River 2.2.3 is the latest release of the Apache River Jini Technology 
>> Starter Kit.  It is a maintenance release that removes the Activation 
>> subsystem and JRMP support. 
>>   
>>  The release artifacts and signatures for the release candidate are 
>> available at: 
>>  https://dist.apacheorg/repos/dist/dev/river/ 
>>   
>>  Although not officially part of the release, convenience binaries for this 
>> release are available in the Apache Maven Repository at 
>> https://repository.apache.org/content/groups/staging/ under ‘net.jini’ and 
>> ‘org.apache.river’.  When the release is approved, these convenience 
>> binaries will be released to Maven Central. 
>>   
>>  [X ] +1: I vote in favour of this release. 
>>  [  ] +0: I am not against this release. 
>>  [  ] -1: I am against this release (please provide discussion and reasons) 
>>   
>>  The vote will remain open for at least 72 hours, ending not sooner than 
>> 0000UTC Feb 12, 2016. 
>>   
> 
> 

Reply via email to