falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shwetha GS <shwetha...@inmobi.com>
Subject Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
Date Thu, 11 Sep 2014 06:04:29 GMT
+1 Verified the build, falcon service

On Wed, Sep 10, 2014 at 10:59 PM, Srikanth Sundarrajan <sriksun@hotmail.com>
wrote:

> Hi Folks,
>     Release package for Falcon 0.5 - RC 5 is now available after resolving
> all the license and notice issues with the help Sebb, Justin Mclean and
> Chris Douglas. Special thanks to them for helping us get this right.
>
> The source tar ball can be downloaded from
> http://people.apache.org/~sriksun/0.5-incubating-rc5, along with
> signature and checksum files.
>
> SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
> MD5 checksum: 33e6d2e4cea237be470020bb69a350f7
>
> Git tag for the release is
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5
>
> More than 140 JIRAs have been closed as part of this release and the
> release notes can be accessed from
> http://s.apache.org/falcon-0.5-release-notes and the change logs are
> available at http://s.apache.org/falcon-0.5-change-log
>
> The release has been signed through key(D2498DC9):
> http://s.apache.org/pgp-sriksun
>
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/falcon/KEYS
>
> Please vote on the release. Vote will expire on Sep 14, 2014 10:00AM IST.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> I am +1
>
> Regards
> Srikanth Sundarrajan
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

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