datafu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eyal Allweil <eyal_allw...@yahoo.com.INVALID>
Subject Re: [VOTE] Apache DataFu 1.3.1 release RC1
Date Sun, 17 Jul 2016 12:48:28 GMT
I did a quick sanity of the udfs that I changed... didn't find anything problematic, and checked
the hash for the jar.

Is there an organized list of what (more) to check?
In any event, based on what I did do, I'm +1. 

    On Saturday, July 16, 2016 1:02 AM, Sam Shah <shahsam@umich.edu> wrote:
 

 Gave it a quick spin... +1.

On Thu, Jul 14, 2016 at 4:00 PM, Matthew Hayes <mhayes@apache.org> wrote:

> Hi all,
>
> I'd like to call a vote to release Apache DataFu 1.3.1 (incubating).
>
> The source release candidate RC1 can be downloaded here:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu-incubating-1.3.1-rc1/
>
> The artifacts (i.e. JARs) corresponding to this release candidate can be
> found here:
>
> https://repository.apache.org/content/repositories/orgapachedatafu-1003/
>
> This has been signed with PGP key 7BA4C7DF, corresponding to
> mhayes@apache.org, which is included in the repository's KEYS file.  This
> key can be found on keyservers, such as:
>
> *http://pgp.mit.edu/pks/lookup?op=get&search=0x7BA4C7DF
> <http://pgp.mit.edu/pks/lookup?op=get&search=0x7BA4C7DF>*
>
> It is also listed here:
>
> https://people.apache.org/keys/group/datafu.asc
>
> The release candidate has been tagged with release-1.3.1-rc1, which has
> been signed with the same key.  I've also created a branch 1.3.1.
>
> For reference, here is a list of all closed JIRAs tagged with 1.3.1:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%201.3.1%20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%20status%20DESC%2C%20priority%20DESC
>
> For a summary of the changes in this release, see:
>
> https://github.com/apache/incubator-datafu/blob/1.3.1/changes.md
>
> This release also addresses feedback from the last release process, namely:
>
> * Using an ASF-related email for code signing
> * Storing the source release in the right place
> * Using a hash other than MD5
> * Releasing artifacts at the same time as the source release
> * Updated release documentation based on above
>
> Please download the release candidate, check the hashes, check the
> signatures, test it, and vote.  The vote will be open for 96 hours (ends on
> July 18th 4 pm PST).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> My vote: +1
>
> Thanks,
> Matthew Hayes
>


  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message