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