Appologies. I'm totally swamped at the moment. I'm not going to get
the time to review this properly and it's my policy to not vote on a
release unless I've verified it (which in this case seems strange
since Ate is so much more thorough than I am).

My chaos will end in 10 days. If you don't have that extra vote by
then please prod me again.

With regret,
Ross

On 2 September 2011 12:42, Franklin, Matthew B. <[email protected]> wrote:
> The 72 hour vote window closes later today.  It would be good if we could get 
> one more Rave mentor vote now so that we don't have to wait for another IPMC 
> member to vote on the incubator list.
>
> -Matt
>
>>-----Original Message-----
>>From: Ate Douma [mailto:[email protected]]
>>Sent: Wednesday, August 31, 2011 6:50 AM
>>To: [email protected]
>>Subject: Re: [DISCUSS] Apache Rave 0.3-incubating Release Candidate
>>
>>On 08/31/2011 12:24 AM, Franklin, Matthew B. wrote:
>>> Discussion thread for vote on 0.3-incubating release candidate.
>>>
>>> For more information on the release process, checkout -
>>> http://www.apache.org/dev/release.html
>>> http://incubator.apache.org/guides/releasemanagement.html
>>>
>>> Some of the things to check before voting are:
>>> - can you run the demo binaries
>>yes
>>> - can you build the contents of source-release.zip and svn tag
>>yes (note: you need to build from both source-release.zips, master and
>>project).
>>
>>> - do all of the staged jars/zips contain the required LICENSE, NOTICE and
>>DISCLAIMER files
>>yes
>>
>>I noticed the LICENSE file embedded in the rave-portal war turned out to be
>>not
>>encoded in UTF-8 but ISO-8859 while all other resources are (and should) be
>>UTF-8.
>>This is only a minor nit. I fixed this already (took me 2 attempts) in trunk 
>>so
>>for future releases it is fine right now.
>>
>>> - are all of the staged jars signed and the signature verifiable
>>yes
>>> - is the signing key in the project's KEYS file and on a public server
>>yes
>>
>>Good work Matt, a clean and complete release!
>>
>>
>
>



-- 
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com

Reply via email to