Errored: apache/geode-examples#376 (rel/v1.9.2.RC1 - e68b827)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #376
Status: Errored

Duration: 1 min and 17 secs
Commit: e68b827 (rel/v1.9.2.RC1)
Author: Jens Deppe
Message: Ordering of repositories appears to be significant

- Specifically, when the conditional repository definition comes ijnto
  play, gradle does not seem to recognize the other defined repositories.

Authored-by: Jens Deppe 

View the changeset: 
https://github.com/apache/geode-examples/compare/rel/v1.9.2.RC1

View the full build log and details: 
https://travis-ci.org/apache/geode-examples/builds/598152058?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.org/account/preferences/unsubscribe?repository=11483039&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Passed: apache/geode-examples#375 (release/1.9.2 - afe2ac8)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #375
Status: Passed

Duration: 20 mins and 22 secs
Commit: afe2ac8 (release/1.9.2)
Author: Jens Deppe
Message: temporarily point to staging repo for CI purposes

View the changeset: 
https://github.com/apache/geode-examples/compare/e68b827f1627...afe2ac857880

View the full build log and details: 
https://travis-ci.org/apache/geode-examples/builds/598151971?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.org/account/preferences/unsubscribe?repository=11483039&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Passed: apache/geode-native#2146 (rel/v1.9.2.RC1 - 8b161cc)

[Travis CI]

Build Update for apache/geode-native
-

Build: #2146
Status: Passed

Duration: 1 hr, 34 mins, and 58 secs
Commit: 8b161cc (rel/v1.9.2.RC1)
Author: Blake Bender
Message: Fix RAT version to reflect new Apache release

Co-authored-by: Jacob Barrett 

View the changeset: 
https://github.com/apache/geode-native/compare/rel/v1.9.2.RC1

View the full build log and details: 
https://travis-ci.org/apache/geode-native/builds/598152128?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the apache/geode-native repository 
going to 
https://travis-ci.org/account/preferences/unsubscribe?repository=11948127&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

[VOTE] Apache Geode 1.9.2.RC1

[Jens Deppe]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.9.2.RC1.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback, including the checks you
performed.

Voting deadline:
3PM PST Sun, October 20 2019.

Please note that we are voting upon the source tag:
rel/v1.9.2.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.2

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1060

GitHub:
https://github.com/apache/geode/tree/rel/v1.9.2.RC1
https://github.com/apache/geode-examples/tree/rel/v1.9.2.RC1
https://github.com/apache/geode-native/tree/rel/v1.9.2.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1 -PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1060
build runAll

Regards
--Jens

Re: [VOTE] Apache Geode 1.9.2.RC1

[Owen Nichols]

I am concerned that this 1.9.2 release contains features that are not in 1.10:
GEODE-7241 Publish war artifacts for geode-web , geode-web-api and 
geode-web-management to Maven Central.
GEODE-7261 Fix compatibility with launching geode-web (admin REST API) when 
Spring 5.x jars are on the classpath.

My concern is that users of these 1.9.2 fixes will be surprised to experience a 
regression when they upgrade to 1.10.0.

This could be addressed by planning a 1.10.1 patch release, or maybe just by 
documenting this caveat as long as the Spring Data project can agree to skip 
over 1.10, but my non-binding vote is -1 until some plan is in place.

-Owen

> On Oct 15, 2019, at 10:47 AM, Jens Deppe  wrote:
> 
> Hello Geode Dev Community,
> 
> This is a release candidate for Apache Geode version 1.9.2.RC1.
> Thanks to all the community members for their contributions to this release!
> 
> Please do a review and give your feedback, including the checks you
> performed.
> 
> Voting deadline:
> 3PM PST Sun, October 20 2019.
> 
> Please note that we are voting upon the source tag:
> rel/v1.9.2.RC1
> 
> Release notes:
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.2
> 
> Source and binary distributions:
> https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1/
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1060
> 
> GitHub:
> https://github.com/apache/geode/tree/rel/v1.9.2.RC1
> https://github.com/apache/geode-examples/tree/rel/v1.9.2.RC1
> https://github.com/apache/geode-native/tree/rel/v1.9.2.RC1
> 
> Pipelines:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-main
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-rc
> 
> Geode's KEYS file containing PGP keys we use to sign the release:
> https://github.com/apache/geode/blob/develop/KEYS
> 
> Command to run geode-examples:
> ./gradlew -PgeodeReleaseUrl=
> https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1 -PgeodeRepositoryUrl=
> https://repository.apache.org/content/repositories/orgapachegeode-1060
> build runAll
> 
> Regards
> --Jens

Re: [VOTE] Apache Geode 1.9.2.RC1

[Udo Kohlmeyer]

Hi there Owen,

Whilst I share your concern of consistence, the Geode user community did 
not notice that the artifacts changed from war -> jar (GEODE-7241). The 
Spring Data Geode project is currently the only downstream project which 
discovered this regression.


As Spring Data Geode 2.2 will not be using any other version than 1.9.x, 
there is no dependency on 1.10.


In addition to this, 1.11 is not that far off, and upon discovery of 
this regression from 1.9.2 -> 1.10, we most likely could be pointing 
them at 1.11 to upgrade.


As for Spring 5 (GEODE-7261), I might agree that we might want to be 
adding that to 1.10.1 patch, but so far I have not seen/heard of any 
users hitting this issue. Maybe it would also fall into the category of 
"wait for 1.11".


--Udo

On 10/15/19 3:05 PM, Owen Nichols wrote:

I am concerned that this 1.9.2 release contains features that are not in 1.10:
GEODE-7241 Publish war artifacts for geode-web , geode-web-api and 
geode-web-management to Maven Central.
GEODE-7261 Fix compatibility with launching geode-web (admin REST API) when 
Spring 5.x jars are on the classpath.

My concern is that users of these 1.9.2 fixes will be surprised to experience a 
regression when they upgrade to 1.10.0.

This could be addressed by planning a 1.10.1 patch release, or maybe just by 
documenting this caveat as long as the Spring Data project can agree to skip 
over 1.10, but my non-binding vote is -1 until some plan is in place.

-Owen


On Oct 15, 2019, at 10:47 AM, Jens Deppe  wrote:

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.9.2.RC1.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback, including the checks you
performed.

Voting deadline:
3PM PST Sun, October 20 2019.

Please note that we are voting upon the source tag:
rel/v1.9.2.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.2

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1060

GitHub:
https://github.com/apache/geode/tree/rel/v1.9.2.RC1
https://github.com/apache/geode-examples/tree/rel/v1.9.2.RC1
https://github.com/apache/geode-native/tree/rel/v1.9.2.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-9-2-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.9.2.RC1 -PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1060
build runAll

Regards
--Jens

Changes to recorded execution times for function stats

[Aaron Lindsey]

Hi Geode devs,

This PR  makes small changes to
the execution times recorded by function stats. I wanted to run this by the
dev list to make sure this will not cause problems for users who rely on
these stats:

   - In ServerFunctionExecutor and ServerRegionFunctionExecutor, we are now
   including validateExecution in the total execution time.
   - In MemberFunctionStreamingMessage, we are now including the code
   leading up to creating the function context in the total execution time.

This would potentially make times reported by function stats appear longer
than prior to this change. Please reply or comment on the PR if anyone sees
a problem with this.

Thanks,
Aaron