You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sentry.apache.org by Kalyan Kumar Kalvagadda <kk...@cloudera.com> on 2017/11/17 16:56:10 UTC
Cutting sentry 2.0.0 off master
Hello all,
All of you are aware that we have decided to release sentry 2.0.0. As a
first step I propose the cut the branch for sentry 2.0.0 off the master
today.
We still have couple of issues that are pending to for 2.0.0 but I would
like to cut it as the tests on the master have become flaky.
Here are jira's that are blocking sentry 2.0.0 release
- *Solr*
1. SENTRY-2042 Support file based Sentry provider for Solr plugin
2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions
* - Hive *
1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin side
2. SENTRY-2048 Bump Hive version to 2.3.2
If we cut the branch, we can limit commits to sentry 2.0.0 to that are
needed and isolate the root cause for the test failures and stabilize 2.0.0
branch.
-Kalyan
Re: Cutting sentry 2.0.0 off master
Posted by Alexander Kolbasov <ak...@cloudera.com>.
We can still create 2.0 branch and just be more selective about what goes
there - we may choose to skip some commits from master.
- Alex.
On Fri, Nov 17, 2017 at 12:24 PM, Sergio Pena <se...@cloudera.com>
wrote:
> +1
>
> Sounds good Kalyan. I'm still finding the test failures and seems related
> to a Jenkins environment more than our code.
>
> On Fri, Nov 17, 2017 at 11:51 AM, Colm O hEigeartaigh <coheigea@apache.org
> >
> wrote:
>
> > SENTRY-1812 is complete and waiting for review (but currently dependent
> on
> > SENTRY-2012 getting merged first). SENTRY-2012 was merged to master
> today,
> > but I had to revert it as it broke the Kafka tests.
> >
> > Colm.
> >
> > On Fri, Nov 17, 2017 at 5:28 PM, Kalyan Kumar Kalvagadda <
> > kkalyan@cloudera.com> wrote:
> >
> > > Colm/Mano Kovacs,
> > >
> > > Do you have an ETA on SENTRY-1812 and SENTRY-2012?
> > >
> > > -Kalyan
> > >
> > > -Kalyan
> > >
> > > On Fri, Nov 17, 2017 at 11:00 AM, Colm O hEigeartaigh <
> > coheigea@apache.org
> > > > wrote:
> > >
> > >> Fine with me, but I'd like to see the fixes for SENTRY-1812 and
> > >> SENTRY-2012
> > >> make it in to 2.0.0 as well.
> > >>
> > >> Colm.
> > >>
> > >> On Fri, Nov 17, 2017 at 4:56 PM, Kalyan Kumar Kalvagadda <
> > >> kkalyan@cloudera.com> wrote:
> > >>
> > >> > Hello all,
> > >> >
> > >> >
> > >> > All of you are aware that we have decided to release sentry 2.0.0.
> As
> > a
> > >> > first step I propose the cut the branch for sentry 2.0.0 off the
> > master
> > >> > today.
> > >> > We still have couple of issues that are pending to for 2.0.0 but I
> > >> would
> > >> > like to cut it as the tests on the master have become flaky.
> > >> > Here are jira's that are blocking sentry 2.0.0 release
> > >> >
> > >> >
> > >> > - *Solr*
> > >> >
> > >> >
> > >> > 1. SENTRY-2042 Support file based Sentry provider for Solr
> plugin
> > >> > 2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry
> permissions
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > * - Hive *
> > >> >
> > >> > 1. SENTRY-1640 Implement HMS Notification barrier on the HMS
> plugin
> > >> side
> > >> > 2. SENTRY-2048 Bump Hive version to 2.3.2
> > >> >
> > >> > If we cut the branch, we can limit commits to sentry 2.0.0 to that
> are
> > >> > needed and isolate the root cause for the test failures and
> stabilize
> > >> 2.0.0
> > >> > branch.
> > >> >
> > >> > -Kalyan
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Colm O hEigeartaigh
> > >>
> > >> Talend Community Coder
> > >> http://coders.talend.com
> > >>
> > >
> > >
> >
> >
> > --
> > Colm O hEigeartaigh
> >
> > Talend Community Coder
> > http://coders.talend.com
> >
>
Re: Cutting sentry 2.0.0 off master
Posted by Sergio Pena <se...@cloudera.com>.
+1
Sounds good Kalyan. I'm still finding the test failures and seems related
to a Jenkins environment more than our code.
On Fri, Nov 17, 2017 at 11:51 AM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> SENTRY-1812 is complete and waiting for review (but currently dependent on
> SENTRY-2012 getting merged first). SENTRY-2012 was merged to master today,
> but I had to revert it as it broke the Kafka tests.
>
> Colm.
>
> On Fri, Nov 17, 2017 at 5:28 PM, Kalyan Kumar Kalvagadda <
> kkalyan@cloudera.com> wrote:
>
> > Colm/Mano Kovacs,
> >
> > Do you have an ETA on SENTRY-1812 and SENTRY-2012?
> >
> > -Kalyan
> >
> > -Kalyan
> >
> > On Fri, Nov 17, 2017 at 11:00 AM, Colm O hEigeartaigh <
> coheigea@apache.org
> > > wrote:
> >
> >> Fine with me, but I'd like to see the fixes for SENTRY-1812 and
> >> SENTRY-2012
> >> make it in to 2.0.0 as well.
> >>
> >> Colm.
> >>
> >> On Fri, Nov 17, 2017 at 4:56 PM, Kalyan Kumar Kalvagadda <
> >> kkalyan@cloudera.com> wrote:
> >>
> >> > Hello all,
> >> >
> >> >
> >> > All of you are aware that we have decided to release sentry 2.0.0. As
> a
> >> > first step I propose the cut the branch for sentry 2.0.0 off the
> master
> >> > today.
> >> > We still have couple of issues that are pending to for 2.0.0 but I
> >> would
> >> > like to cut it as the tests on the master have become flaky.
> >> > Here are jira's that are blocking sentry 2.0.0 release
> >> >
> >> >
> >> > - *Solr*
> >> >
> >> >
> >> > 1. SENTRY-2042 Support file based Sentry provider for Solr plugin
> >> > 2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions
> >> >
> >> >
> >> >
> >> >
> >> > * - Hive *
> >> >
> >> > 1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin
> >> side
> >> > 2. SENTRY-2048 Bump Hive version to 2.3.2
> >> >
> >> > If we cut the branch, we can limit commits to sentry 2.0.0 to that are
> >> > needed and isolate the root cause for the test failures and stabilize
> >> 2.0.0
> >> > branch.
> >> >
> >> > -Kalyan
> >> >
> >>
> >>
> >>
> >> --
> >> Colm O hEigeartaigh
> >>
> >> Talend Community Coder
> >> http://coders.talend.com
> >>
> >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Cutting sentry 2.0.0 off master
Posted by Colm O hEigeartaigh <co...@apache.org>.
SENTRY-1812 is complete and waiting for review (but currently dependent on
SENTRY-2012 getting merged first). SENTRY-2012 was merged to master today,
but I had to revert it as it broke the Kafka tests.
Colm.
On Fri, Nov 17, 2017 at 5:28 PM, Kalyan Kumar Kalvagadda <
kkalyan@cloudera.com> wrote:
> Colm/Mano Kovacs,
>
> Do you have an ETA on SENTRY-1812 and SENTRY-2012?
>
> -Kalyan
>
> -Kalyan
>
> On Fri, Nov 17, 2017 at 11:00 AM, Colm O hEigeartaigh <coheigea@apache.org
> > wrote:
>
>> Fine with me, but I'd like to see the fixes for SENTRY-1812 and
>> SENTRY-2012
>> make it in to 2.0.0 as well.
>>
>> Colm.
>>
>> On Fri, Nov 17, 2017 at 4:56 PM, Kalyan Kumar Kalvagadda <
>> kkalyan@cloudera.com> wrote:
>>
>> > Hello all,
>> >
>> >
>> > All of you are aware that we have decided to release sentry 2.0.0. As a
>> > first step I propose the cut the branch for sentry 2.0.0 off the master
>> > today.
>> > We still have couple of issues that are pending to for 2.0.0 but I
>> would
>> > like to cut it as the tests on the master have become flaky.
>> > Here are jira's that are blocking sentry 2.0.0 release
>> >
>> >
>> > - *Solr*
>> >
>> >
>> > 1. SENTRY-2042 Support file based Sentry provider for Solr plugin
>> > 2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions
>> >
>> >
>> >
>> >
>> > * - Hive *
>> >
>> > 1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin
>> side
>> > 2. SENTRY-2048 Bump Hive version to 2.3.2
>> >
>> > If we cut the branch, we can limit commits to sentry 2.0.0 to that are
>> > needed and isolate the root cause for the test failures and stabilize
>> 2.0.0
>> > branch.
>> >
>> > -Kalyan
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Cutting sentry 2.0.0 off master
Posted by Kalyan Kumar Kalvagadda <kk...@cloudera.com>.
Colm/Mano Kovacs,
Do you have an ETA on SENTRY-1812 and SENTRY-2012?
-Kalyan
-Kalyan
On Fri, Nov 17, 2017 at 11:00 AM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> Fine with me, but I'd like to see the fixes for SENTRY-1812 and SENTRY-2012
> make it in to 2.0.0 as well.
>
> Colm.
>
> On Fri, Nov 17, 2017 at 4:56 PM, Kalyan Kumar Kalvagadda <
> kkalyan@cloudera.com> wrote:
>
> > Hello all,
> >
> >
> > All of you are aware that we have decided to release sentry 2.0.0. As a
> > first step I propose the cut the branch for sentry 2.0.0 off the master
> > today.
> > We still have couple of issues that are pending to for 2.0.0 but I would
> > like to cut it as the tests on the master have become flaky.
> > Here are jira's that are blocking sentry 2.0.0 release
> >
> >
> > - *Solr*
> >
> >
> > 1. SENTRY-2042 Support file based Sentry provider for Solr plugin
> > 2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions
> >
> >
> >
> >
> > * - Hive *
> >
> > 1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin
> side
> > 2. SENTRY-2048 Bump Hive version to 2.3.2
> >
> > If we cut the branch, we can limit commits to sentry 2.0.0 to that are
> > needed and isolate the root cause for the test failures and stabilize
> 2.0.0
> > branch.
> >
> > -Kalyan
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Cutting sentry 2.0.0 off master
Posted by Colm O hEigeartaigh <co...@apache.org>.
Fine with me, but I'd like to see the fixes for SENTRY-1812 and SENTRY-2012
make it in to 2.0.0 as well.
Colm.
On Fri, Nov 17, 2017 at 4:56 PM, Kalyan Kumar Kalvagadda <
kkalyan@cloudera.com> wrote:
> Hello all,
>
>
> All of you are aware that we have decided to release sentry 2.0.0. As a
> first step I propose the cut the branch for sentry 2.0.0 off the master
> today.
> We still have couple of issues that are pending to for 2.0.0 but I would
> like to cut it as the tests on the master have become flaky.
> Here are jira's that are blocking sentry 2.0.0 release
>
>
> - *Solr*
>
>
> 1. SENTRY-2042 Support file based Sentry provider for Solr plugin
> 2. SENTRY-1480 A upgrade tool to migrate Solr/Sentry permissions
>
>
>
>
> * - Hive *
>
> 1. SENTRY-1640 Implement HMS Notification barrier on the HMS plugin side
> 2. SENTRY-2048 Bump Hive version to 2.3.2
>
> If we cut the branch, we can limit commits to sentry 2.0.0 to that are
> needed and isolate the root cause for the test failures and stabilize 2.0.0
> branch.
>
> -Kalyan
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com