+1
> On Jun 6, 2015, at 8:58 AM, Dilli Arumugam <[email protected]> wrote: > > +0 > Considering the known problems which have been subsequently fixed but not > in this release candidate > Dilli > >> On 6/5/15 11:34 PM, "Gautam Borad" <[email protected]> wrote: >> >> +1 >> >> On Sat, Jun 6, 2015 at 11:17 AM, Dilli Arumugam >> <[email protected]> >> wrote: >> >>> Selva, >>> Just wanted to bring them to attention. >>> I leave the decision to your judgment as release manager. >>> Thanks >>> Dilli >>> >>>> On 6/5/15 10:43 PM, "Selvamohan Neethiraj" <[email protected]> wrote: >>>> >>>> Dilli: >>>> >>>> I understand that some of these fixes needs to be covered in the >>> release. >>>> Can we add them in 0.5.1 release (soon after 0.5.0) ? >>>> >>>> >>>> Thanks, >>>> Selva- >>>> >>>> From: Dilli Arumugam <[email protected]> >>>> Reply-To: "[email protected]" >>>> <[email protected]> >>>> Date: Saturday, June 6, 2015 at 1:38 AM >>>> To: "[email protected]" >>> <[email protected]> >>>> Subject: Re: [VOTE] Release Apache Ranger 0.5.0 (incubating) - release >>>> candidate 3 (dev group vote) >>>> >>>> Reviewed the Jiras fixed in 0.5, after RANGER-525. >>>> Some of the fixes that have gone in after RANGER-525 look important. >>>> >>>> E.g >>>> https://issues.apache.org/jira/browse/RANGER-530 >>>> >>>> Access-type "all" should imply rest of the permissions in Hive >>>> >>>> >>>> https://issues.apache.org/jira/browse/RANGER-531 >>>> >>>> Legacy plugins unable to download policies >>>> >>>> >>>> https://issues.apache.org/jira/browse/RANGER-532 >>>> >>>> Storm Plugin Installation failed with error NoClassDefFoundError >>>> >>>> >>>> https://issues.apache.org/jira/browse/RANGER-533 >>>> >>>> Hbase plugin: if user does not have family-level access to any family >>> in a >>>> table then user may be incorrectly denied access done at table/family >>>> level during get or scan (patch available) >>>> >>>> >>>> https://issues.apache.org/jira/browse/RANGER-534 >>>> >>>> Upgrade does not migrate some policies >>>> >>>> >>>> Would it be appropriate to have another release candidate? >>>> Thanks >>>> Dilli >>>> >>>>> On 6/5/15 10:28 PM, "Ramesh Mani" <[email protected]> wrote: >>>>> >>>>> >>>>> +1 >>>>> >>>>> Thanks, >>>>> Ramesh >>>>> >>>>> On 6/3/15, 3:46 AM, "Selvamohan Neethiraj" >>> <[email protected]> >>>>> wrote: >>>>> >>>>>> All: >>>>>> >>>>>> As another blocker bug >>>>>> (RANGER-525<https://issues.apache.org/jira/browse/RANGER-525>) was >>>>>> fixed >>>>>> today, I have included recent fixes for the Ranger Release 0.5.0 >>>>>> (incubating) - Release Candidate # 3: >>>>>> >>>>>> The ranger-0.5.0-rc3 release candidate is build from ranger-0.5 >>> branch >>>>>> and is available with the following artifacts up for a project vote: >>>>>> >>>>>> Git tag for the release: >>> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlo >>>>>> g >>>>>> ; >>>>>> h=refs/tags/ranger-0.5.0-rc3 >>>>>> >>>>>> Source release: >>> >>>>>> http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5. >>>>>> 0 >>> . >>>>>> t >>>>>> a >>>>>> r.gz >>>>>> >>>>>> PGP Signature: >>> >>>>>> http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5. >>>>>> 0 >>> . >>>>>> t >>>>>> a >>>>>> r.gz.asc >>>>>> >>>>>> >>>>>> MD5/SHA hash: >>> >>>>>> http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5. >>>>>> 0 >>> . >>>>>> t >>>>>> a >>>>>> r.gz.mds >>>>>> >>>>>> >>>>>> Keys to verify the signature of the release artifact are available >>> at: >>>>>> https://people.apache.org/keys/group/ranger.asc >>>>>> >>>>>> The vote will be open for at least 72 hours or until necessary >>> number >>>>>> of >>>>>> votes is reached. >>>>>> [ ] +1 approve >>>>>> [ ] +0 no opinion >>>>>> [ ] -1 disapprove (and reason why) >>>>>> >>>>>> Here is my +1 (binding) >>>>>> >>>>>> Thanks >>>>>> Selva- >> >> >> -- >> Regards, >> Gautam. > >
