Odg: Next release

Thanks for the info! BR, Mario Šalje: Ernest Burghardt Poslano: 17. ožujka 2020. 0:06 Prima: dev@geode.apache.org Predmet: Re: Next release Hi Mario, There is still some work to be done to ensure performance is on par with previous releases... here are a few

Re: Next release

Hi Mario, There is still some work to be done to ensure performance is on par with previous releases... here are a few tickets related to the efforts https://issues.apache.org/jira/browse/GEODE-7763 https://issues.apache.org/jira/browse/GEODE-7832 https://issues.apache.org/jira/browse/GEODE-7853

Next release

Hi geode-dev, When we will have Apache Geode 1.12.0 release? I saw that all test passed and the last commit was before 4 days(typos correct). Are we waiting fix for some critical issue or something else? Thanks and BR, Mario

Re: Next release 1.7.0

Great! Thank you! Barbara > On May 18, 2018, at 12:18 PM, Nabarun Nag wrote: > > Hi Barbara, > > I volunteer to be the release manager for Apache Geode 1.7.0. > > Regards > Naba > > > On Fri, May 18, 2018 at 9:02 AM Barbara Pruijn > wrote: > Hi all, > > Nice wor

Re: Next release 1.7.0

Hi Barbara, I volunteer to be the release manager for Apache Geode 1.7.0. Regards Naba [image: giphy.gif] On Fri, May 18, 2018 at 9:02 AM Barbara Pruijn wrote: > Hi all, > > Nice work on getting the 1.6.0 release out the door! Next up is 1.7.0. > We’ve finished around 200 issues since the las

Re: Next release 1.7.0

I agree, I think we need to do a release. I ran into GEODE-3563 setting up an SSL-enabled cluster and I’m anxious to get that fix out. Here’s the full list of fixes: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012318420%20AND%20fixVersion%20%3D%2012343041%20ORDER%20BY%20priority%20

Next release 1.7.0

Hi all, Nice work on getting the 1.6.0 release out the door! Next up is 1.7.0. We’ve finished around 200 issues since the last release. Any one want to volunteer for release manager? If you haven’t done this before and would like to try, please review [1]. Barbara [1] https://cwiki.apac

Re: Next release: 1.5.0

Thanks, John. I did a round of updates for this release and expect we can continue do this in subsequent releases. Bundled dependencies: Commons Lang is at *3.7;* Geode is at 2.6 Log4j is at *2.10.0*; Geode is at 2.8.2 Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final

Re: Next release: 1.5.0

I also noticed that there are several outdated dependency versions yet... AssertJ is at *3.9.1; *Geode is at 3.8.0 Commons Lang is at *3.7;* Geode is at 2.6 JSON Path is at *2.4.0*; Geode is at 2.2.0 Log4j is at *2.10.0*; Geode is at 2.8.2 Mockito is at *2.15.0*; Geode is at 2.8.9 Netty is at *4.

Re: Next release: 1.5.0

Looks like there are some things broken related to serialization filtering as well on the release branch: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/2

Re: Next release: 1.5.0

I don't think this should wait since it affects downstream artifacts (already)... Pivotal GemFire -> PCC. As I stated, I am will have the changes prepared a few hours. This is pretty low risk from Apache Geode's side but is imperative for Spring/PCC users. On Tue, Mar 6, 2018 at 8:40 AM, Alexand

Re: Next release: 1.5.0

John, how much of an issue would it be if the change was added one month from now? On Tue, Mar 6, 2018 at 8:36 AM, John Blum wrote: > I have 1 addition (planning to submit a PR for review) for the 1.5 release > that is imperative for *Spring Data for Apache Geode*, and specifically, > client-sid

Re: Next release: 1.5.0

I have 1 addition (planning to submit a PR for review) for the 1.5 release that is imperative for *Spring Data for Apache Geode*, and specifically, client-side Cluster Configuration Push [1]. Details to follow soon; will file a ticket in JIRA. -j [1] https://docs.spring.io/spring-data/geode/doc

Re: Next release: 1.5.0

Could you make the pipeline public? Anthony > On Mar 5, 2018, at 12:46 PM, Sean Goller wrote: > > 1.5.0 pipeline is up and running, please take a look at it and let the list > know if there are problems. > > https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0 > > On Mon,

Re: Next release: 1.5.0

1.5.0 pipeline is up and running, please take a look at it and let the list know if there are problems. https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0 On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker wrote: > LGTM > > > On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar > wro

Re: Next release: 1.5.0

LGTM > On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar wrote: > > Thanks Dave! > > All, I have created a release branch ( > https://github.com/apache/geode/tree/release/1.5.0) Please review. > > On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes wrote: > >> Status on the 3 doc issues: >> GEODE-4737 / G

Re: Next release: 1.5.0

Thanks Dave! All, I have created a release branch ( https://github.com/apache/geode/tree/release/1.5.0) Please review. On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes wrote: > Status on the 3 doc issues: > GEODE-4737 / GEODE-3915: JSON args in gfsh - Done > GEODE-4101: redirect-output - Done > GEOD

Re: Next release: 1.5.0

Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Done GEODE-4101: redirect-output - Done GEODE-3948: client timeout - Done On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar wrote: > I will take up the release management task for 1.5.0 > > On Mon, Feb 26, 2018 at 5:03 PM

Re: Next release: 1.5.0

I will take up the release management task for 1.5.0 On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes wrote: > Status on the 3 doc issues: > GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered > GEODE-4101: redirect-output - Dave, in process, on track > GEODE-3948: client timeout -

Re: Next release: 1.5.0

Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered GEODE-4101: redirect-output - Dave, in process, on track GEODE-3948: client timeout - Dave, in process. Probably on track - will keep you posted On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker wrote:

Re: Next release: 1.5.0

Just checking in as we’re approaching the end of February. We’ve finished around 200 issues and enhancements with 3 documentation updates open [1]. Is this a good time for another release? Any takers to do the release management tasks for 1.5.0? Anthony [1] https://issues.apache.org/jira/pro

Next release: 1.5.0

Hi all, Nice work on getting the 1.4.0 release out the door! Next up is 1.5.0. Any one want to volunteer for release manager? If you haven’t done this before and would like to try, please review [1]. I’ve been advocating for more frequent releases. I’d love see a March release—which means

Re: Next release: 1.4.0

I’ve updated the Jenkins nightly and release jobs. Please ping me if you have any questions. Anthony > On Jan 5, 2018, at 10:00 AM, Anthony Baker wrote: > > +1 > > It should be pretty easy to clone the current pipeline for the 1.4.0 release > branch. > > I’ll plan to update the Jenkins jo

Re: Next release: 1.4.0

. > > > > >> > Currently there are 14 issues that are marked for 1.4.0. If you > > are > > > > >> working > > > > >> > on any of these, can you please update the JIRA? > > > > >> > > > > > >> htt

Re: Next release: 1.4.0

=92&projectKey=GEODE&view=planning&selectedIssue= GEODE-3688&versions=visible&selectedVersion=12341842 Thanks! On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker wrote: Bump. Any volunteers? If not, I’ll do this. Anthony On Nov 22, 2017, at 1:48 PM, Anthony Baker wrote: W

Re: Next release: 1.4.0

;>>>> review and merge. > >>>>>> > >>>>>> Sarge > >>>>>> > >>>>>>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar >>> > >>>>>> wrote: > >>>>>>> &g

Re: Next release: 1.4.0

ter release. > > >>>>> > > >>>>> On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge < > > >>>> mdo...@pivotal.io> > > >>>>> wrote: > > >>>>> > > >>>>>> What sort of

Re: Next release: 1.4.0

gt;>>> review and merge. > >>>>>> > >>>>>> Sarge > >>>>>> > >>>>>>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar >>> > >>>>>> wrote: > >>>>>>> > >

Re: Next release: 1.4.0

t;> >>>>>>> I would like to volunteer as a release manager. >>>>>>> Currently there are 14 issues that are marked for 1.4.0. If you >> are >>>>>> working >>>>>>> on any of these, can you please update the JIR

Re: Next release: 1.4.0

> are > > > >> working > > > >> > on any of these, can you please update the JIRA? > > > >> > > > > >> https://issues.apache.org/jira/secure/RapidBoard.jspa? > > > rapidView=92&projectKey=GEODE&view=planning&

Re: Next release: 1.4.0

=GEODE&view=planning&selectedIssue= > > GEODE-3688&versions=visible&selectedVersion=12341842 > > >> > > > >> > Thanks! > > >> > > > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker > > >> wrote: >

Re: Next release: 1.4.0

spa? > rapidView=92&projectKey=GEODE&view=planning&selectedIssue= > GEODE-3688&versions=visible&selectedVersion=12341842 > >> > > >> > Thanks! > >> > > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker > >> w

Re: Next release: 1.4.0

/jira/secure/RapidBoard.jspa?rapidView=92&projectKey=GEODE&view=planning&selectedIssue=GEODE-3688&versions=visible&selectedVersion=12341842 >> > >> > Thanks! >> > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker >> wrote: >> >

Re: Next release: 1.4.0

y Baker wrote: > > > >> Bump. Any volunteers? If not, I’ll do this. > >> > >> Anthony > >> > >> > >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker wrote: > >>> > >>> We released Geode 1.3.0 at the end of October

Re: Next release: 1.4.0

42 AM Anthony Baker wrote: > >> Bump. Any volunteers? If not, I’ll do this. >> >> Anthony >> >> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker wrote: >>> >>> We released Geode 1.3.0 at the end of October. Our next release will be

Re: Next release: 1.4.0

e=GEODE-3688&versions=visible&selectedVersion=12341842 Thanks! On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker wrote: > Bump. Any volunteers? If not, I’ll do this. > > Anthony > > > > On Nov 22, 2017, at 1:48 PM, Anthony Baker wrote: > > > > We released

Re: Next release: 1.4.0

Bump. Any volunteers? If not, I’ll do this. Anthony > On Nov 22, 2017, at 1:48 PM, Anthony Baker wrote: > > We released Geode 1.3.0 at the end of October. Our next release will be > 1.4.0. Questions: > > 1) Who wants to volunteer as a release manager? > 2) What do

Re: Next release: 1.4.0

I'd like to see it include the recently completed work on indexing nested objects in the Apache Lucene integration. Early Dec sounds good to me. -- Mike Stolz On Wed, Nov 22, 2017 at 4:48 PM, Anthony Baker wrote: > We released Geode 1.3.0 at the end of October. Our next release

Next release: 1.4.0

We released Geode 1.3.0 at the end of October. Our next release will be 1.4.0. Questions: 1) Who wants to volunteer as a release manager? 2) What do we want to include in the release? 3) When do we want to do this? IMO, let's should shoot for an early Dec release. Anthony

Re: Question regarding the next release

The community is working hard to ensure that backwards compatibility is preserved. There are currently 2 open issues remaining to be fixed: https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012318420%20AND%20fixVersion%20%3D%2012339257%20ORDER%20BY%20pri

Question regarding the next release

Hi, Is there an expected date for release of 1.2? Are there any backward compatibility issues in this version? If so, are they documented separately from the other issues? Thanks, Roi This message and the information contained herein is proprietary and confidential and subject to the Amdocs p

Re: The next release (v1.1.0)

Type for jSON > >> document(Need to document system property) > >> > >> Thanks.HItesh > >> > >> > >> > >> From: Hitesh Khamesra > >> To: "dev@geode.apache.org" > >> Sent: Monday, January 16, 2017 12:35 PM > >&

Re: The next release (v1.1.0)

sort field while creating pdxType for jSON >> document(Need to document system property) >> >> Thanks.HItesh >> >> >> >> From: Hitesh Khamesra >> To: "dev@geode.apache.org" >> Sent: Monday, January 16, 2017 12:35 PM >>

Re: The next release (v1.1.0)

ability to sort field while creating pdxType for jSON >> > document(Need to document system property) >> > >> > Thanks.HItesh >> > >> > >> > >> > From: Hitesh Khamesra >> > To: "dev@geode.apache.o

Re: The next release (v1.1.0)

; GEODE-2353 Verify no clear-text passwords in documentation > > GEODE-2282 Provide ability to sort field while creating pdxType for jSON > > document(Need to document system property) > > > > Thanks.HItesh > > > > > > > > From: Hitesh Khamesra >

Re: The next release (v1.1.0)

anks.HItesh > > > > From: Hitesh Khamesra > To: "dev@geode.apache.org" > Sent: Monday, January 16, 2017 12:35 PM > Subject: Re: The next release (v1.1.0) > > Update: We are waiting on following tickets for first release candidate. > > 1. GEODE-229

Re: The next release (v1.1.0)

) Thanks.HItesh From: Hitesh Khamesra To: "dev@geode.apache.org" Sent: Monday, January 16, 2017 12:35 PM Subject: Re: The next release (v1.1.0) Update: We are waiting on following tickets for first release candidate. 1.  GEODE-2296 GetFunctionAttribute command is throwing an

Re: The next release (v1.1.0)

4.  GEODE-1965 Create backward-compatibility unit test framework Thanks.HItesh From: Anthony Baker To: dev@geode.apache.org Sent: Monday, January 9, 2017 9:49 AM Subject: Re: The next release (v1.1.0) Updates: 1) I did a first round of changes on GEODE-2142, should be enough for

Re: The next release (v1.1.0)

> On Jan 9, 2017, at 10:53 AM, Hitesh Khamesra > wrote: > > let me try it out this time. Any instruction to follow? > Thanks.HItesh > > > From: Anthony Baker > To: dev@geode.apache.org > Sent: Monday, January 9, 2017 9:49 AM > Subject: Re: The next release

Re: The next release (v1.1.0)

let me try it out this time. Any instruction to follow? Thanks.HItesh From: Anthony Baker To: dev@geode.apache.org Sent: Monday, January 9, 2017 9:49 AM Subject: Re: The next release (v1.1.0) Updates: 1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0. 2

Re: The next release (v1.1.0)

; > > Regarding the release manager, I can do the dirty work if no one else > wants to volunteer :-) > > > > Anthony > > > > [1] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%

Re: The next release (v1.1.0)

%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker wrote: >> >> Now that graduation is done (!!), we need to organize our next release. I >> propose we focus on completing the transition to T

Re: The next release (v1.1.0)

n is done (!!), we need to organize our next release. I > propose we focus on completing the transition to TLP and cleaning up > “incubating" references. The sequence would look something like this: > > 1) Transition the git repo, mailing lists, etc. > 2) Update incubati

Re: The next release (v1.1.0)

FYI, I started work on GEODE-2156 to remove references to “incubating”. Feel free to jump in on the feature branch (feature/GEODE-2156). I don’t plan to merge this to develop until the infrastructure changes are ready (see INFRA-12937). Anthony > On Nov 25, 2016, at 7:44 PM, Nitin Lamba wro

Re: The next release (v1.1.0)

e? Thanks, Nitin [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail On Fri, Nov 25, 2016 at 12:45 PM, Dor Ben Dov wrote: > Hi Anthony > > Thanks for the answer. > > Dor > > Original Message ---- > > Subjec

Re: The next release (v1.1.0)

Hi Anthony Thanks for the answer. Dor Original Message Subject: Re: The next release (v1.1.0) From: Anthony Baker Date: 25 בנוב' 2016, 16:44 To: dev@geode.apache.org Hi Dor, I want to stress that the transition was from an Apache Incubator subproject to an Apach

Re: The next release (v1.1.0)

> Sent: יום ג 22 נובמבר 2016 16:44 > To: geode > Subject: Re: The next release (v1.1.0) > > Transitioning from an incubating project to a top-level project means we keep > doing exactly what we’ve been doing—except that now the project is > responsible for managing its

Re: The next release (v1.1.0)

+1... We all want this project to be the best it can be. On 11/23/16 09:07, Dan Smith wrote: Dor - I don't think any of the active committers are planning on leaving. We're working on this project because we want it to thrive, and graduation is one more thing that will help it grow!

Re: The next release (v1.1.0)

nuing to contribute? > Regards, > Dor > > -Original Message- > From: Anthony Baker [mailto:aba...@pivotal.io] > Sent: יום ג 22 נובמבר 2016 16:44 > To: geode > Subject: Re: The next release (v1.1.0) > > Transitioning from an incubating project to a top-level projec

RE: The next release (v1.1.0)

To: geode Subject: Re: The next release (v1.1.0) Transitioning from an incubating project to a top-level project means we keep doing exactly what we’ve been doing—except that now the project is responsible for managing itself. We will be transitioning a few resources such as mailing lists and

Re: The next release (v1.1.0)

age- > From: Anthony Baker [mailto:aba...@pivotal.io] > Sent: יום ב 21 נובמבר 2016 19:26 > To: dev@geode.apache.org > Subject: The next release (v1.1.0) > > Now that graduation is done (!!), we need to organize our next release. I > propose we focus on completing t

RE: The next release (v1.1.0)

Anthony, What are the actual implications of this transition to the tlp ? Regards, Dor -Original Message- From: Anthony Baker [mailto:aba...@pivotal.io] Sent: יום ב 21 נובמבר 2016 19:26 To: dev@geode.apache.org Subject: The next release (v1.1.0) Now that graduation is done (!!), we

The next release (v1.1.0)

Now that graduation is done (!!), we need to organize our next release. I propose we focus on completing the transition to TLP and cleaning up “incubating" references. The sequence would look something like this: 1) Transition the git repo, mailing lists, etc. 2) Update incubating refer