+1 On Thu, May 14, 2020 at 8:54 AM Donal Evans <doev...@pivotal.io> wrote:
> Thanks for the explanation, Robert. Also, I realised I never explicitly > said it in my earlier post, but this is a +1 from me > > On Thu, May 14, 2020 at 8:05 AM Joris Melchior <jmelch...@vmware.com> > wrote: > > > This seems like a good thing to have. > > > > +1 > > ________________________________ > > From: Robert Houghton <rhough...@pivotal.io> > > Sent: May 13, 2020 17:32 > > To: dev@geode.apache.org <dev@geode.apache.org>; Mario Ivanac > > <mario.iva...@est.tech> > > Subject: [DISCUSS] enable GitHub PR blocking on API breaking changes > > > > We have enabled this job on the develop and support 1.13 branches, and it > > is going well. I would like this to be a blocking job for our pull > > requests. > > > > Are there any issues around this test that we want to address, or reasons > > to *not* have it be a blocking job in the PR pipeline? > > > > To seed the conversation, there is an issue I am working on with @Mario > > Ivanac <mario.iva...@est.tech> regarding exemptions to the Gradle task. > > > > I would like to have a [VOTE] by end of week on this. > > >
