Re: release 1.2

There is a backward-compatibility problem that we need to address before the release can go out. It prevents the subscription queues in a 1.2 server from draining if the subscribed client is running an old version. Barry and I are both working on this issue. See https://issues.apache.org/jir

Re: release 1.2

I have staged a v1.2 doc update for the Apache Geode website, using RC 1 versions of the User Guide and the Javadocs. Later release candidates are unlikely to require doc changes, other than the Wiki-based relnotes, so I'm nearly certain this will be the final version. When we merge or rename this

Re: release 1.2

> On Jun 14, 2017, at 4:59 PM, Anthony Baker wrote: > > Agreed. Please merge to release/1.2.0 when ready. > > Anthony > Hi everyone, Please contribute to the ‘crowd-sourced’ releases notes at: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes

Re: release 1.2

Agreed. Please merge to release/1.2.0 when ready. Anthony > On Jun 14, 2017, at 1:46 PM, Lynn Hughes-Godfrey > wrote: > > We would like to include the fix for (GEODE-3072) Events do not get removed > from the client queue when 1.0 clients connect to 1.2 servers > > On Wed, Jun 14, 2017 at 12

Re: release 1.2

We would like to include the fix for (GEODE-3072) Events do not get removed from the client queue when 1.0 clients connect to 1.2 servers On Wed, Jun 14, 2017 at 12:25 PM, Fred Krone wrote: > Reviewing our JTA transaction manager implementation during a recent issue > we thought it would be usef

Re: release 1.2

Reviewing our JTA transaction manager implementation during a recent issue we thought it would be useful to log message for users when our implementation is being used (which is by default but potentially unknown). It's small but not critical -- we thought we might get it in if the 1.2 release li

Re: release 1.2

> On Jun 14, 2017, at 12:03 PM, Eric Shu wrote: > > I'd like to include GEODE-2301 in the release 1.2.0 (deprecate GEODE > implementation of JTA transaction manager) > > -Eric Thanks Eric. Can you make a case for why this change needs to go into 1.2.0? We’re pretty locked down on 1.2.0 chan

Re: release 1.2

ercome this SSL should be disabled for the cluster, > which is not the best way to proceed. > >> > >> Thanks, > >> Vahram. > >> > >> -Original Message- > >> From: Anthony Baker [mailto:aba...@pivotal.io <mailto:aba...@pivotal.io > >

Re: release 1.2

SSL should be disabled for the cluster, which is not the best >> way to proceed. >> >> Thanks, >> Vahram. >> >> -Original Message----- >> From: Anthony Baker [mailto:aba...@pivotal.io <mailto:aba...@pivotal.io>] >> Sent: Monday, Ju

Re: release 1.2

SSL should be disabled for the cluster, which is not the best way to > proceed. > > Thanks, > Vahram. > > -Original Message- > From: Anthony Baker [mailto:aba...@pivotal.io <mailto:aba...@pivotal.io>] > Sent: Monday, June 12, 2017 7:42 PM > To: dev@geod

RE: release 1.2

, 2017 7:42 PM To: dev@geode.apache.org Subject: Re: release 1.2 Got it, thanks! Anthony > On Jun 10, 2017, at 7:15 PM, Udo Kohlmeyer wrote: > > I thought we had moved GEODE-3052 to a later release, given that we have a > work around for this. > > --Udo > > > On 6

Re: release 1.2

Got it, thanks! Anthony > On Jun 10, 2017, at 7:15 PM, Udo Kohlmeyer wrote: > > I thought we had moved GEODE-3052 to a later release, given that we have a > work around for this. > > --Udo > > > On 6/10/17 10:15, Anthony Baker wrote: >> Status update: >> >> We have 2 issues left: GEODE-30

Re: release 1.2

I thought we had moved GEODE-3052 to a later release, given that we have a work around for this. --Udo On 6/10/17 10:15, Anthony Baker wrote: Status update: We have 2 issues left: GEODE-3054 and GEODE-3052. We also had a clean run of the Geode-release jenkins job. So as soon as we can fi

Re: release 1.2

Sounds good. I believe GEODE-3054 is already fixed on develop and release/1.2.0. - Jared > On Jun 10, 2017, at 10:15 AM, Anthony Baker wrote: > > Status update: > > We have 2 issues left: GEODE-3054 and GEODE-3052. We also had a clean run > of the Geode-release jenkins job. So as soon as

Re: release 1.2

Status update: We have 2 issues left: GEODE-3054 and GEODE-3052. We also had a clean run of the Geode-release jenkins job. So as soon as we can finish off these issues and get another clean run through Jenkins I’ll create a release candidate. How does early next week sound? Anthony > On J

Re: release 1.2

Sounds good. Please cherry-pick these changes onto release/1.2.0 when ready. Anthony > On Jun 8, 2017, at 3:15 PM, Jared Stewart wrote: > > I think we probably ought to include GEODE-3045 > as well. > >> On Jun 8, 2017, at 3:12 PM, Kennet

Re: release 1.2

I think we probably ought to include GEODE-3045 as well. > On Jun 8, 2017, at 3:12 PM, Kenneth Howe wrote: > > I think we should also include the fix for GEODE-3054 in 1.2. This is a bug > that was introduced in the recent changes to the Gfs

Re: release 1.2

I think we should also include the fix for GEODE-3054 in 1.2. This is a bug that was introduced in the recent changes to the Gfsh parser, and affects Windows pathnames specified in options to gfsh commands. https://issues.apache.org/jira/browse/GEODE-3054

release 1.2

I'd like to include the fix for GEODE-3052 in the 1.2 release. It's under review now and has passed new tests and is in precheckin testing. https://issues.apache.org/jira/browse/GEODE-3052 "Restarting 2 locators within 1s of each other causes potential locator split brain"