rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Woonsan Ko <woon_...@yahoo.com>
Subject Re: [DISCUSS] Apache Rave 0.19 Release Candidate
Date Fri, 11 Jan 2013 14:31:27 GMT

> From: Matt Franklin <m.ben.franklin@gmail.com>
>To: dev@rave.apache.org; Woonsan Ko <woonsan@apache.org> 
>Sent: Friday, January 11, 2013 8:17 AM
>Subject: Re: [DISCUSS] Apache Rave 0.19 Release Candidate
>On Wed, Jan 9, 2013 at 10:23 PM, Woonsan Ko <woon_san@yahoo.com> wrote:
>> I've verified those things and everything seems okay.
>> But, I have one minor thing: I'm afraid the fix version for RAVE-818 should not be
>> If we publish the release notes url like we did for 0.18, then including RAVE-818
can be misleading.
>Any particular reason?  I was thinking we would link to the mongo
>documentation from the download section...

Oh, then I must have been confused. Because I noticed its subtasks were unresolved, I just
thought the issue has not been resolved yet.

If there's a working solution with MongoDB, then it's fair to include it. And, a document
link in a comment in the JIRA issue must be helpful.



>> Cheers,
>> Woonsan
>>> From: Matt Franklin <m.ben.franklin@gmail.com>
>>>To: dev@rave.apache.org
>>>Sent: Monday, January 7, 2013 6:35 PM
>>>Subject: [DISCUSS] Apache Rave 0.19 Release Candidate
>>>Discussion thread for vote on 0.19 release candidate.
>>>For more information on the release process, checkout -
>>>Some of the things to check before voting are:
>>>- can you run the demo binaries
>>>- can you build the contents of source-release.zip and svn tag
>>>- do all of the staged jars/zips contain the required LICENSE and NOTICE files
>>>- are all of the staged artifacts signed and the signature verifiable
>>>- is the signing key in the project's KEYS file and on a public server

View raw message