Re: [ANNOUNCE] Apache Geode 1.4.0

Awesome! -- Akihiro Kitada | Staff Customer Engineer | +81 80 3716 3736 Support.Pivotal.io | Mon-Fri 9:00am to 5:30pm JST | 1-877-477-2269 [image: support] [image: twitter] [image: linkedin]

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #819 was SUCCESSFUL (with 2324 tests). Change made by John Blum.

--- Spring Data GemFire > Nightly-ApacheGeode > #819 was successful. --- Scheduled with changes by John Blum. 2326 tests in total.

Volunteer Request: Write Draft Board Report For February 2018

Hi Everyone, Great job on getting 1.4.0 released, which makes it good timing that we are scheduled to report to the Apache board for the board meeting on February 21st. Template: https://cwiki.apache.org/confluence/display/GEODE/ASF+Board+Report +Template Previous Reports:

Re: Naming unit tests and integration tests

Should we make a pass over all of the tests and rename them to follow the conventions we come up with?  It would take some time, and maybe access to Pivotal's old Trac issue tracker in order to rename files with "Bug" and numbers for a name. On 2/5/18 12:28 PM, Kirk Lund wrote: I've been

Re: Naming unit tests and integration tests

I've been using the name FooDistributedTest for new dunit tests. I should've included that. For RegressionTests, I've been including the GEODE jira ticket number and summary in the javadocs on the test class. I'll include that in any changes I make to the wiki. On Mon, Feb 5, 2018 at 11:55 AM,

Re: Naming unit tests and integration tests

These seem like sensible ideas to me.  I especially don't like tests named after bug numbers.  I do like a pointer to relevant tickets in test comments/javadocs though. We also have DUnitTest.  Some designation in the name that it's using the dunit infrastructure is often useful to me. 

Re: Naming unit tests and integration tests

Another valuable naming standard is the use FooRegressionTest for tests that are specific to reproducing a bug and verifying its fix. Don't use Bug007IntegrationTest. Use something description like QueryShouldNotIncludeTXSetsRegressionTest (if you want a separate test class for the bug which is

Re: MigrationClient and MigrationServer

Yeah we made a change to our diskstore format right around 6.0 that caused customers to have to migrate all their persistent stores. I don't think we have any plans to attempt any migrations from pre-6.0 any more ;) +1 for deleting these -- Mike Stolz Principal Engineer, GemFire Product Lead

Re: MigrationClient and MigrationServer

+1 to remove. UNLESS we want to start a migration module, which could contain all the scripts or classes we require to do some migration on/off line... --Udo On Mon, Feb 5, 2018 at 10:08 AM, Anilkumar Gingade wrote: > Its used for data migration from one version to

Re: MigrationClient and MigrationServer

Its used for data migration from one version to another...Don't see any mention of this in docs or any tools built around it. +1 for removal. -Anil. On Fri, Feb 2, 2018 at 4:38 PM, Kirk Lund wrote: > I just ran across two classes in org.apache.geode.internal package: > *

[ANNOUNCE] Apache Geode 1.4.0

The Apache Geode community is pleased to announce the availability of Apache Geode 1.4.0. Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with