Re: [PROPOSAL] bring GEODE-8091 to support branches

..and 1.12. On Mon, May 11, 2020 at 6:09 PM Dave Barnes wrote: > OK, Jinmei. Three of those plus-ones is the magic minimum. > Please add your change to 1.13. > Dave > > > On Mon, May 11, 2020 at 4:20 PM Donal Evans wrote: > >> +1 >> >> On Mon, May 11, 2020 at 4:11 PM Anilkumar Gingade >>

Re: [PROPOSAL] bring GEODE-8091 to support branches

OK, Jinmei. Three of those plus-ones is the magic minimum. Please add your change to 1.13. Dave On Mon, May 11, 2020 at 4:20 PM Donal Evans wrote: > +1 > > On Mon, May 11, 2020 at 4:11 PM Anilkumar Gingade > wrote: > > > +1 > > > > On Mon, May 11, 2020 at 4:10 PM Jinmei Liao wrote: > > > > >

Re: [PROPOSAL] bring GEODE-8091 to support branches

+1 On Mon, May 11, 2020 at 4:11 PM Anilkumar Gingade wrote: > +1 > > On Mon, May 11, 2020 at 4:10 PM Jinmei Liao wrote: > > > https://issues.apache.org/jira/browse/GEODE-8091 > > > > We've had users that were trying to use the > > "--load-cluster-configuration-from-dir=true" when starting up a

Re: [PROPOSAL] bring GEODE-8091 to support branches

+1 On Mon, May 11, 2020 at 4:10 PM Jinmei Liao wrote: > https://issues.apache.org/jira/browse/GEODE-8091 > > We've had users that were trying to use the > "--load-cluster-configuration-from-dir=true" when starting up a locator > with a security manager and came across this failure on Geode1.12

Re: [PROPOSAL] bring GEODE-8091 to support branches

+1 > On May 11, 2020, at 4:09 PM, Jinmei Liao wrote: > > https://issues.apache.org/jira/browse/GEODE-8091 > > We've had users that were trying to use the > "--load-cluster-configuration-from-dir=true" when starting up a locator > with a security manager and came across this failure on

[PROPOSAL] bring GEODE-8091 to support branches

https://issues.apache.org/jira/browse/GEODE-8091 We've had users that were trying to use the "--load-cluster-configuration-from-dir=true" when starting up a locator with a security manager and came across this failure on Geode1.12 and would this to be fixed. Can I get a few +1s to port this back

Re: Discussion - Change Public API Before Initial Release

For closure this has been cherry-picked into support/1.13. Thanks, Jake > On May 11, 2020, at 10:47 AM, Dave Barnes wrote: > > Plenty of votes, go ahead, Jake, and add this to the support/1.13 branch. > > On Mon, May 11, 2020 at 8:36 AM Joris Melchior wrote: > >> +1 >>

Re: Our May 2020 report to the board

Thank you Dave for putting together the report !! Thank you all for putting together those amazing blogs and all the Apache Geode contributors. Regards Naba Get Outlook for iOS From: Karen Miller Sent: Monday, May 11, 2020 2:30:35 PM

Our May 2020 report to the board

Apache Geode developers, please thank Dave Barnes for putting together the May 2020 board report that I filed today. Here is the contents of the report: ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides

Re: Proposal to bring GEODE-8016 to support branches

Thanks! Change has been backported to 1.13 and 1.12. Downstream projects can now use the new version selector syntax consistently across 1.12, 1.13, and 1.14. To recap, that means if you are a downstream project and you want the latest “nightly build” (formerly -SNAPSHOT) of Geode 1.12,

Re: Proposal to bring GEODE-8016 to support branches

Looks good, Owen. Go ahead and add this to 1.13. On Mon, May 11, 2020 at 9:49 AM Robert Houghton wrote: > Yes please! +1 > > On Mon, May 11, 2020 at 2:46 AM Darrel Schneider > wrote: > > > +1 > > > > On Sun, May 10, 2020 at 10:05 PM Dick Cavender > > wrote: > > > > > +1 > > > > > > On Sat,

Re: Proposal to bring GEODE-8068 to support/1.13

Go ahead, Patrick, and add this to 1.13. On Mon, May 11, 2020 at 8:36 AM Joris Melchior wrote: > +1 > > From: Patrick Johnson > Sent: May 8, 2020 17:40 > To: dev@geode.apache.org > Subject: Proposal to bring GEODE-8068 to support/1.13 > > I’d like to bring

Re: Discussion - Change Public API Before Initial Release

Plenty of votes, go ahead, Jake, and add this to the support/1.13 branch. On Mon, May 11, 2020 at 8:36 AM Joris Melchior wrote: > +1 > > From: Jacob Barrett > Sent: May 8, 2020 21:26 > To: dev@geode.apache.org > Subject: Discussion - Change Public API Before

Re: Proposal to bring GEODE-8016 to support branches

Yes please! +1 On Mon, May 11, 2020 at 2:46 AM Darrel Schneider wrote: > +1 > > On Sun, May 10, 2020 at 10:05 PM Dick Cavender > wrote: > > > +1 > > > > On Sat, May 9, 2020 at 6:42 PM Owen Nichols wrote: > > > > > Last week develop was successfully migrated from publishing -SNAPSHOT > to > >

Re: Proposal to bring GEODE-8068 to support/1.13

+1 From: Patrick Johnson Sent: May 8, 2020 17:40 To: dev@geode.apache.org Subject: Proposal to bring GEODE-8068 to support/1.13 I’d like to bring GEODE-8068 to support/1.13. This commit reverts two prior commits (GEODE-8033 and GEODE-8044). GEODE-8033 and

Re: Discussion - Change Public API Before Initial Release

+1 From: Jacob Barrett Sent: May 8, 2020 21:26 To: dev@geode.apache.org Subject: Discussion - Change Public API Before Initial Release Hey Ya’ll, We have a new API going into 1.13 that has an inconsistency I want to address before we are stuck with it. The

Re: Proposal to bring GEODE-8016 to support branches

+1 On Sun, May 10, 2020 at 10:05 PM Dick Cavender wrote: > +1 > > On Sat, May 9, 2020 at 6:42 PM Owen Nichols wrote: > > > Last week develop was successfully migrated from publishing -SNAPSHOT to > > publishing -build.nnn, as discussed on the dev list. > > > > I propose that we bring the same