You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sentry.apache.org by Sergio Pena <se...@cloudera.com> on 2017/07/26 20:57:00 UTC
DISCUSSION: Prepare master for next release (2.0.0)
Hi,
Now that branch-1.8 has been created, we need to prepare the current master
branch for the next major release. However, the current master won't be
used for that, and the new sentry-ha-redesign branch will become master.
We'd like to do this as soon as possible. This change will be disruptive,
and all contributors will have to update their master with the new one.
Can we do this today or tomorrow? Anytime no later than Friday so that we
have the most updated master to the community.
- Sergio
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Hao Hao <ha...@cloudera.com>.
+1
Best,
Hao
On Thu, Jul 27, 2017 at 1:38 AM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> +1.
>
> Colm.
>
> On Wed, Jul 26, 2017 at 10:45 PM, Vamsee Yarlagadda <va...@cloudera.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Vamsee
> >
> > On Wed, Jul 26, 2017 at 2:11 PM, Na Li <li...@cloudera.com> wrote:
> >
> > > Sergio,
> > >
> > > I agree we should do it soon. Can you send out a notice right before
> it?
> > So
> > > we will submit the changes to master instead of sentry-ha-redesign for
> > 2.0
> > >
> > > Thanks,
> > >
> > > Lina
> > >
> > > On Wed, Jul 26, 2017 at 3:57 PM, Sergio Pena <sergio.pena@cloudera.com
> >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Now that branch-1.8 has been created, we need to prepare the current
> > > master
> > > > branch for the next major release. However, the current master won't
> be
> > > > used for that, and the new sentry-ha-redesign branch will become
> > master.
> > > >
> > > > We'd like to do this as soon as possible. This change will be
> > disruptive,
> > > > and all contributors will have to update their master with the new
> one.
> > > >
> > > > Can we do this today or tomorrow? Anytime no later than Friday so
> that
> > we
> > > > have the most updated master to the community.
> > > >
> > > > - Sergio
> > > >
> > >
> >
> >
> >
> > --
> > Thanks,
> > Vamsee
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Colm O hEigeartaigh <co...@apache.org>.
+1.
Colm.
On Wed, Jul 26, 2017 at 10:45 PM, Vamsee Yarlagadda <va...@cloudera.com>
wrote:
> +1
>
> Thanks,
> Vamsee
>
> On Wed, Jul 26, 2017 at 2:11 PM, Na Li <li...@cloudera.com> wrote:
>
> > Sergio,
> >
> > I agree we should do it soon. Can you send out a notice right before it?
> So
> > we will submit the changes to master instead of sentry-ha-redesign for
> 2.0
> >
> > Thanks,
> >
> > Lina
> >
> > On Wed, Jul 26, 2017 at 3:57 PM, Sergio Pena <se...@cloudera.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Now that branch-1.8 has been created, we need to prepare the current
> > master
> > > branch for the next major release. However, the current master won't be
> > > used for that, and the new sentry-ha-redesign branch will become
> master.
> > >
> > > We'd like to do this as soon as possible. This change will be
> disruptive,
> > > and all contributors will have to update their master with the new one.
> > >
> > > Can we do this today or tomorrow? Anytime no later than Friday so that
> we
> > > have the most updated master to the community.
> > >
> > > - Sergio
> > >
> >
>
>
>
> --
> Thanks,
> Vamsee
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Vamsee Yarlagadda <va...@cloudera.com>.
+1
Thanks,
Vamsee
On Wed, Jul 26, 2017 at 2:11 PM, Na Li <li...@cloudera.com> wrote:
> Sergio,
>
> I agree we should do it soon. Can you send out a notice right before it? So
> we will submit the changes to master instead of sentry-ha-redesign for 2.0
>
> Thanks,
>
> Lina
>
> On Wed, Jul 26, 2017 at 3:57 PM, Sergio Pena <se...@cloudera.com>
> wrote:
>
> > Hi,
> >
> > Now that branch-1.8 has been created, we need to prepare the current
> master
> > branch for the next major release. However, the current master won't be
> > used for that, and the new sentry-ha-redesign branch will become master.
> >
> > We'd like to do this as soon as possible. This change will be disruptive,
> > and all contributors will have to update their master with the new one.
> >
> > Can we do this today or tomorrow? Anytime no later than Friday so that we
> > have the most updated master to the community.
> >
> > - Sergio
> >
>
--
Thanks,
Vamsee
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Na Li <li...@cloudera.com>.
Sergio,
I agree we should do it soon. Can you send out a notice right before it? So
we will submit the changes to master instead of sentry-ha-redesign for 2.0
Thanks,
Lina
On Wed, Jul 26, 2017 at 3:57 PM, Sergio Pena <se...@cloudera.com>
wrote:
> Hi,
>
> Now that branch-1.8 has been created, we need to prepare the current master
> branch for the next major release. However, the current master won't be
> used for that, and the new sentry-ha-redesign branch will become master.
>
> We'd like to do this as soon as possible. This change will be disruptive,
> and all contributors will have to update their master with the new one.
>
> Can we do this today or tomorrow? Anytime no later than Friday so that we
> have the most updated master to the community.
>
> - Sergio
>
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Kalyan Kumar Kalvagadda <kk...@cloudera.com>.
+1
-Kalyan
On Wed, Jul 26, 2017 at 4:05 PM, Alexander Kolbasov <ak...@cloudera.com>
wrote:
> +1. Important note - anyone who is working on Sentry will need to get a
> fresh clone.
>
> On Wed, Jul 26, 2017 at 10:57 PM, Sergio Pena <se...@cloudera.com>
> wrote:
>
> > Hi,
> >
> > Now that branch-1.8 has been created, we need to prepare the current
> master
> > branch for the next major release. However, the current master won't be
> > used for that, and the new sentry-ha-redesign branch will become master.
> >
> > We'd like to do this as soon as possible. This change will be disruptive,
> > and all contributors will have to update their master with the new one.
> >
> > Can we do this today or tomorrow? Anytime no later than Friday so that we
> > have the most updated master to the community.
> >
> > - Sergio
> >
>
Re: DISCUSSION: Prepare master for next release (2.0.0)
Posted by Alexander Kolbasov <ak...@cloudera.com>.
+1. Important note - anyone who is working on Sentry will need to get a
fresh clone.
On Wed, Jul 26, 2017 at 10:57 PM, Sergio Pena <se...@cloudera.com>
wrote:
> Hi,
>
> Now that branch-1.8 has been created, we need to prepare the current master
> branch for the next major release. However, the current master won't be
> used for that, and the new sentry-ha-redesign branch will become master.
>
> We'd like to do this as soon as possible. This change will be disruptive,
> and all contributors will have to update their master with the new one.
>
> Can we do this today or tomorrow? Anytime no later than Friday so that we
> have the most updated master to the community.
>
> - Sergio
>