Re: Cutting sentry 2.0.0 off master

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 wrote: > +1 > > Sounds good Kalyan. I'm still finding the test failures and seems

Re: Cutting sentry 2.0.0 off master

+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 wrote: > SENTRY-1812 is complete and waiting for review (but currently dependent on > SENTRY-2012

Re: Cutting sentry 2.0.0 off master

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 < kkal...@cloudera.com> wrote:

Re: Cutting sentry 2.0.0 off master

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 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

Re: Cutting sentry 2.0.0 off master

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 < kkal...@cloudera.com> wrote: > Hello all, > > > All of you are aware that we have decided to release sentry 2.0.0. As a >

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.