We are removing the "?" in the syntax and continue on this route of
implementation: className followed by the json representation of the
properties to initialize the class.
A pull request has been opened regarding this:
https://github.com/apache/geode/pull/1327
On Fri, Jan 26, 2018 at 12:38 PM,
I would like to change the ExpirationAction to a true Enum object, but this
class is used by ExpirationAttributes which is a DataSerializable, and
making the change fails the rolling upgrade tests. Anyone knows a good
example that I can follow to update a DataSerializable object?
Specifically, how
https://cwiki.apache.org/confluence/display/GEODE/Managing+Backward+Compatibility
On 1/29/18 8:59 AM, Jinmei Liao wrote:
I would like to change the ExpirationAction to a true Enum object, but this
class is used by ExpirationAttributes which is a DataSerializable, and
making the change fails the
Question:
How many versions of the User Documentation and the Javadocs do we need to
see on the Geode Docs page (http://geode.apache.org/docs)?
The current scheme has two policies:
- For the User Documentation, there's a link for each of four versions:
1.0, 1.1, 1.2 and 1.3. There will soon be a f
I'm fine with the proposal. It would be nice if there was a way to navigate to
user documentation for older versions; perhaps just rely on Google? ;)
Sarge
> On 29 Jan, 2018, at 10:39, Dave Barnes wrote:
>
> Question:
> How many versions of the User Documentation and the Javadocs do we need to
Maybe we could have a link at the bottom that goes to a full list?
On Mon, Jan 29, 2018 at 11:10 AM, Michael William Dodge
wrote:
> I'm fine with the proposal. It would be nice if there was a way to
> navigate to user documentation for older versions; perhaps just rely on
> Google? ;)
>
> Sarge
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/107
---
Spring Data GemFire > Nightly-ApacheGeode > #812 was successful.
---
Scheduled
2326 tests in total.
https://build.spring.io/browse/SGF-NAG-812/
--
This
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/164
After fixing the security concerns in the first release candidate, this is
the second release candidate for Apache Geode, version 1.4.0.
Thanks to all the community members for their contributions to this
release!
*** Please download, test and vote by Thursday, Feb 1, 1400 hrs
US Pacific. ***
It
+1
Looks good to me. Ran geode-release-check, verified potential security
issue is resolved, concourse job passed.
-Dan
On Mon, Jan 29, 2018 at 4:08 PM, Swapnil Bawaskar
wrote:
> After fixing the security concerns in the first release candidate, this is
> the second release candidate for Apach
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/166
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/108
13 matches
Mail list logo
