@ranger.apache.org" , "
> cohei...@apache.org"
> Date: Thursday, February 9, 2017 at 9:40 AM
> To: "dev@ranger.apache.org"
>
> Subject: Re: Prep for ranger-0.7 release ...
>
> Did you push the branch? It's not available yet as can be seen here:
> https://g
Sorry, I missed the ‘git push’ … It should be available now.
Thanks,
Selva-
From: Colm O hEigeartaigh
Reply-To: "dev@ranger.apache.org" ,
"cohei...@apache.org"
Date: Thursday, February 9, 2017 at 9:40 AM
To: "dev@ranger.apache.org"
Subject: Re: Prep for r
ail to the dev@ranger.apache.org.
>
> Thanks,
> Selva-
>
> From: "Lal,Alok(allal)"
> Reply-To: "dev@ranger.apache.org"
> Date: Wednesday, February 8, 2017 at 1:08 PM
> To: "dev@ranger.apache.org" , "cohei...@apache.org"
>
>
pache.org"
Subject: Re: Prep for ranger-0.7 release ...
@Selva, Sounds good.
On 2/8/17, 9:15 AM, "Colm O hEigeartaigh" wrote:
Sounds good to me. Perhaps we could wait a short period of time before
enforcing "strict" cherry-picking, so that some of the more rece
@Selva, Sounds good.
On 2/8/17, 9:15 AM, "Colm O hEigeartaigh" wrote:
Sounds good to me. Perhaps we could wait a short period of time before
enforcing "strict" cherry-picking, so that some of the more recent patches
can appear in 0.7.
Colm.
On Wed, Feb 8, 2017 at 3
Sounds good to me. Perhaps we could wait a short period of time before
enforcing "strict" cherry-picking, so that some of the more recent patches
can appear in 0.7.
Colm.
On Wed, Feb 8, 2017 at 3:53 PM, Selvamohan Neethiraj
wrote:
> Rangers:
>
> As we are planning to do a release of ranger 0.7
Rangers:
As we are planning to do a release of ranger 0.7 soon, I would like to create
a branch ranger-0.7 for stabilizing the release.
All of the fixes should go into the master which will track for our next major
release (planning to call it as 1.0.0 ) and if needed will get cherry-picked
