ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From PradeeP AgrawaL <pradeepagrawal8...@gmail.com>
Subject Re: Ranger 1.1 release
Date Wed, 27 Jun 2018 04:16:22 GMT
+1


Regards,
PradeeP

On 25 June 2018 at 15:04, Colm O hEigeartaigh <coheigea@apache.org> wrote:

> +1.
>
> Colm.
>
> On Sun, Jun 24, 2018 at 9:18 PM, Zsombor Gegesy <zsombor@apache.org>
> wrote:
>
> > +1 - I believe in the "release early release often" mantra :)
> >
> >
> > Regards,
> >  Zsombor
> >
> > On Sun, Jun 24, 2018 at 5:56 PM, Srikanth Venkat <
> svenkat@hortonworks.com>
> > wrote:
> >
> > > +1, it would be nice to have a Ranger release baseline that aligns with
> > > Atlas 1.0.
> > > Thanks Vel for taking the initiative!
> > >
> > > Thx
> > > Srikanth Venkat
> > > svenkat@hortonworks.com
> > >
> > > On 6/22/18, 10:24 PM, "Balaji Ganesan" <balaji.ganesan03@gmail.com>
> > > wrote:
> > >
> > >     +1. Vel, thanks for taking the initiative.
> > >
> > >     On Fri, Jun 22, 2018 at 7:51 PM Jianhua Peng <
> pengjianhua@apache.org
> > >
> > > wrote:
> > >
> > >     > +1
> > >     >
> > >     > Thank you,
> > >     > Jianhua Peng.
> > >     >
> > >     > On 2018/06/22 16:25:45, Velmurugan Periasamy <vel@apache.org>
> > wrote:
> > >     > > Rangers:
> > >     > >
> > >     > > Now that support for Atlas 1.0 is added (
> > >     > https://issues.apache.org/jira/browse/RANGER-2136 <
> > >     > https://issues.apache.org/jira/browse/RANGER-2136>), I propose
> to
> > > release
> > >     > Ranger 1.1 (tentative first week of July).
> > >     > >
> > >     > > I request the community to resolve open JIRA’s marked for 1.1
> in
> > > the
> > >     > next couple of weeks or move them to next release. My proposal is
> > to
> > > call
> > >     > next release 2.0 and update master to 2.0.0-SNAPSHOT.
> > >     > >
> > >     > > Thank you,
> > >     > > Vel
> > >     >
> > >
> > >
> > >
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

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