Re: [DISCUSS] New List for Commit and CI Emails

[Dan Smith]

I was curious about the stats for bot vs. humans on the dev list. Out of
915 messages, looks like we're about 50% robot.

I'm still be in favor of not sending these messages to dev@geode. Long time
members have probably already created a mail filter by now (I know I have)
so we're only hurting newbies by sending a bunch of messages.

1) apac...@gmail.com 241
2) Spring CI 109
3) Kirk Lund 63
4) Apache Jenkins Server 51
5) Anthony Baker 41
6) Dan Smith 40
7) Travis CI 38

Geode unit tests completed in 'develop/IntegrationTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/298

Re: [DISCUSS] New List for Commit and CI Emails

[Anthony Baker]

Looking at other ASF projects it’s pretty rare to see much beyond 
user/dev/issues/commits.  Cassandra has a ‘pr’ list.


> On Mar 20, 2018, at 2:50 PM, Nick Reich  wrote:
> 
> +1
> I use an email filter (from:apachegeod...@gmail.com) to move all the
> automated CI messages to a different section of my inbox, but having a
> fully distinct email list, if possible, would be even nicer.
> 
> On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
> wrote:
> 
>> Hi all,
>> 
>> I'm wondering if it would be possible to have a separate list for commit
>> announcements, CI emails and similar automated messages, and keep this
>> mailing list for discussion. It would make it easier to filter email, and I
>> think it might help improve the discussion. I know I've missed messages
>> sent to this list in the flood of email. What do you think? Who's in charge
>> of lists and gets to make those decisions?
>> 
>> Thanks,
>> Galen
>> 

Re: [VOTE] Apache Geode 1.5.0 RC1

[Anthony Baker]

md5 generation is already removed from geode, just need to do this for 
geode-examples.

Anthony


> On Mar 20, 2018, at 3:30 PM, Swapnil Bawaskar  wrote:
> 
> Removed!
> 
> I also filed a JIRA to not generate the md5 checksum file going forward:
> https://issues.apache.org/jira/browse/GEODE-4903
> 
> On Tue, Mar 20, 2018 at 3:18 PM Dan Smith  wrote:
> 
>> It looks like we are still generating .md5 files. That doesn't necessarily
>> need to hold up this release (you could just delete them from SVN), but
>> we're not supposed to be distributing .md5 files anymore.
>> 
>> http://www.apache.org/dev/release-distribution#sigs-and-sums
>> 
>> -Dan
>> 
>> On Tue, Mar 20, 2018 at 3:09 PM, Swapnil Bawaskar 
>> wrote:
>> 
>>> This is the first release candidate for Apache Geode, version 1.5.0.
>>> Thanks to all the community members for their contributions to this
>>> release!
>>> 
>>> *** Please download, test and vote by Friday, March 23, 1500 hrs
>>> US Pacific. ***
>>> 
>>> It fixes 234 issues. release notes can be found at:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12318420=12342395
>>> 
>>> Note that we are voting upon the source tags: rel/v1.5.0.RC1
>>> https://github.com/apache/geode/tree/rel/v1.5.0.RC1
>>> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1
>>> 
>>> Commit ID:
>>> 4ef51dacd79ff69336fb024f3d4b07271e90 (geode)
>>> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
>>> 
>>> Source and binary files:
>>> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1
>>> 
>>> Maven staging repo:
>>> https://repository.apache.org/content/repositories/orgapachegeode-1038
>>> 
>>> 
>>> Geode's KEYS file containing PGP keys we use to sign the release:
>>> https://github.com/apache/geode/blob/develop/KEYS
>>> 
>>> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
>>> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
>>> 
>> 

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #862 was SUCCESSFUL (with 2379 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #862 was successful.
---
Scheduled
2381 tests in total.

https://build.spring.io/browse/SGF-NAG-862/





--
This message is automatically generated by Atlassian Bamboo

Re: [VOTE] Apache Geode 1.5.0 RC1

[Anthony Baker]

The release dir looked fine to me.  Were you looking at maven?  Those are 
automatically generated during the upload and we don’t have explicit control 
over them.  I’ve spent hours just trying to get rid of the hash files for the 
signatures :(

Anthony


> On Mar 20, 2018, at 3:18 PM, Dan Smith  wrote:
> 
> It looks like we are still generating .md5 files. That doesn't necessarily
> need to hold up this release (you could just delete them from SVN), but
> we're not supposed to be distributing .md5 files anymore.
> 
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> 
> -Dan
> 
> On Tue, Mar 20, 2018 at 3:09 PM, Swapnil Bawaskar 
> wrote:
> 
>> This is the first release candidate for Apache Geode, version 1.5.0.
>> Thanks to all the community members for their contributions to this
>> release!
>> 
>> *** Please download, test and vote by Friday, March 23, 1500 hrs
>> US Pacific. ***
>> 
>> It fixes 234 issues. release notes can be found at:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12318420=12342395
>> 
>> Note that we are voting upon the source tags: rel/v1.5.0.RC1
>> https://github.com/apache/geode/tree/rel/v1.5.0.RC1
>> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1
>> 
>> Commit ID:
>> 4ef51dacd79ff69336fb024f3d4b07271e90 (geode)
>> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
>> 
>> Source and binary files:
>> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1
>> 
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachegeode-1038
>> 
>> 
>> Geode's KEYS file containing PGP keys we use to sign the release:
>> https://github.com/apache/geode/blob/develop/KEYS
>> 
>> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
>> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
>> 

Re: [VOTE] Apache Geode 1.5.0 RC1

[Swapnil Bawaskar]

Removed!

I also filed a JIRA to not generate the md5 checksum file going forward:
https://issues.apache.org/jira/browse/GEODE-4903

On Tue, Mar 20, 2018 at 3:18 PM Dan Smith  wrote:

> It looks like we are still generating .md5 files. That doesn't necessarily
> need to hold up this release (you could just delete them from SVN), but
> we're not supposed to be distributing .md5 files anymore.
>
> http://www.apache.org/dev/release-distribution#sigs-and-sums
>
> -Dan
>
> On Tue, Mar 20, 2018 at 3:09 PM, Swapnil Bawaskar 
> wrote:
>
> > This is the first release candidate for Apache Geode, version 1.5.0.
> > Thanks to all the community members for their contributions to this
> > release!
> >
> > *** Please download, test and vote by Friday, March 23, 1500 hrs
> > US Pacific. ***
> >
> > It fixes 234 issues. release notes can be found at:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12318420=12342395
> >
> > Note that we are voting upon the source tags: rel/v1.5.0.RC1
> > https://github.com/apache/geode/tree/rel/v1.5.0.RC1
> > https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1
> >
> > Commit ID:
> > 4ef51dacd79ff69336fb024f3d4b07271e90 (geode)
> > 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachegeode-1038
> >
> >
> > Geode's KEYS file containing PGP keys we use to sign the release:
> > https://github.com/apache/geode/blob/develop/KEYS
> >
> > Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> > Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Swapnil Bawaskar]

I don't think we should send ci to a different email list for it to be
ignored. We ideally should be in a place where emails from ci are not the
norm but an exception which prompts immediate action.

On Tue, Mar 20, 2018 at 3:05 PM Dan Smith  wrote:

> +1 to removing all automated messages from dev@geode
>
> I think we've already shunted commit messages to commits@geode and jira
> issue updates to issues@geode. What I see now is mostly messages related
> to
> ci. Should we create a new ci@geode mailing list, or send those messages
> to
> some other mailing list?
>
> If we want to create a new list, I think the next step is to file a ticket
> with infra after we come to a consensus. Unless our illustrious leader Mark
> has access to do that :)
>
> To move the CI emails to the the new list, we'll have to update concourse,
> jenkins, travis, and spring CI it looks like.
>
> -Dan
>
> On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
> wrote:
>
> > Hi all,
> >
> > I'm wondering if it would be possible to have a separate list for commit
> > announcements, CI emails and similar automated messages, and keep this
> > mailing list for discussion. It would make it easier to filter email,
> and I
> > think it might help improve the discussion. I know I've missed messages
> > sent to this list in the flood of email. What do you think? Who's in
> charge
> > of lists and gets to make those decisions?
> >
> > Thanks,
> > Galen
> >
>

Re: [VOTE] Apache Geode 1.5.0 RC1

[Dan Smith]

It looks like we are still generating .md5 files. That doesn't necessarily
need to hold up this release (you could just delete them from SVN), but
we're not supposed to be distributing .md5 files anymore.

http://www.apache.org/dev/release-distribution#sigs-and-sums

-Dan

On Tue, Mar 20, 2018 at 3:09 PM, Swapnil Bawaskar 
wrote:

> This is the first release candidate for Apache Geode, version 1.5.0.
> Thanks to all the community members for their contributions to this
> release!
>
> *** Please download, test and vote by Friday, March 23, 1500 hrs
> US Pacific. ***
>
> It fixes 234 issues. release notes can be found at:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12342395
>
> Note that we are voting upon the source tags: rel/v1.5.0.RC1
> https://github.com/apache/geode/tree/rel/v1.5.0.RC1
> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1
>
> Commit ID:
> 4ef51dacd79ff69336fb024f3d4b07271e90 (geode)
> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1038
>
>
> Geode's KEYS file containing PGP keys we use to sign the release:
> https://github.com/apache/geode/blob/develop/KEYS
>
> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
>

[VOTE] Apache Geode 1.5.0 RC1

[Swapnil Bawaskar]

This is the first release candidate for Apache Geode, version 1.5.0.
Thanks to all the community members for their contributions to this
release!

*** Please download, test and vote by Friday, March 23, 1500 hrs
US Pacific. ***

It fixes 234 issues. release notes can be found at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12342395

Note that we are voting upon the source tags: rel/v1.5.0.RC1
https://github.com/apache/geode/tree/rel/v1.5.0.RC1
https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1

Commit ID:
4ef51dacd79ff69336fb024f3d4b07271e90 (geode)
4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)

Source and binary files:
https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1

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


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

Release Signed with Key: pub 4096R/18F902DB 2016-04-07
Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB

Re: [DISCUSS] New List for Commit and CI Emails

[Dan Smith]

+1 to removing all automated messages from dev@geode

I think we've already shunted commit messages to commits@geode and jira
issue updates to issues@geode. What I see now is mostly messages related to
ci. Should we create a new ci@geode mailing list, or send those messages to
some other mailing list?

If we want to create a new list, I think the next step is to file a ticket
with infra after we come to a consensus. Unless our illustrious leader Mark
has access to do that :)

To move the CI emails to the the new list, we'll have to update concourse,
jenkins, travis, and spring CI it looks like.

-Dan

On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
wrote:

> Hi all,
>
> I'm wondering if it would be possible to have a separate list for commit
> announcements, CI emails and similar automated messages, and keep this
> mailing list for discussion. It would make it easier to filter email, and I
> think it might help improve the discussion. I know I've missed messages
> sent to this list in the flood of email. What do you think? Who's in charge
> of lists and gets to make those decisions?
>
> Thanks,
> Galen
>

Re: [DISCUSS] New List for Commit and CI Emails

[Nick Reich]

+1
I use an email filter (from:apachegeod...@gmail.com) to move all the
automated CI messages to a different section of my inbox, but having a
fully distinct email list, if possible, would be even nicer.

On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
wrote:

> Hi all,
>
> I'm wondering if it would be possible to have a separate list for commit
> announcements, CI emails and similar automated messages, and keep this
> mailing list for discussion. It would make it easier to filter email, and I
> think it might help improve the discussion. I know I've missed messages
> sent to this list in the flood of email. What do you think? Who's in charge
> of lists and gets to make those decisions?
>
> Thanks,
> Galen
>

Re: [Discussion] Improving Spotless to be Even More Beautiful

[Galen O'Sullivan]

On Tue, Mar 20, 2018 at 9:06 AM, Patrick Rhomberg 
wrote:

>
> @Galen, I had thought it already did that.
>

I guess it does. I never knew. Excellent!

[DISCUSS] New List for Commit and CI Emails

[Galen O'Sullivan]

Hi all,

I'm wondering if it would be possible to have a separate list for commit
announcements, CI emails and similar automated messages, and keep this
mailing list for discussion. It would make it easier to filter email, and I
think it might help improve the discussion. I know I've missed messages
sent to this list in the flood of email. What do you think? Who's in charge
of lists and gets to make those decisions?

Thanks,
Galen

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/213

Passed: jinmeiliao/geode#285 (queue - 9c8037b)

[Travis CI]

Build Update for jinmeiliao/geode
-

Build: #285
Status: Passed

Duration: 19 minutes and 50 seconds
Commit: 9c8037b (queue)
Author: Jinmei Liao
Message: GEODE-4901: increase the wait time for the newly created queue to be 
ready.

View the changeset: 
https://github.com/jinmeiliao/geode/compare/6214a43be9d3^...9c8037bd1bd9

View the full build log and details: 
https://travis-ci.org/jinmeiliao/geode/builds/355994725?utm_source=email_medium=notification

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications







This email was sent to dev@geode.apache.org (mailto:dev@geode.apache.org)
unsubscribe from this list 
(http://clicks.travis-ci.com/track/unsub.php?u=14313403=148c20a5ea2640ccb6a1a397fe522202.J7HZbFy6S8dTlH7tD%2B7uJ8FM8HM%3D=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Ddev%2540geode.apache.org)

Geode is back at SpringOne Platform 2018!

[Jagdish Mirani]

Hello Geode enthusiasts:
Join us this September 24-27, in Washington D.C. for our biggest conference
yet, and experience for yourself a variety of Geode talks and sessions.

For the Geode community, learning and sharing go hand-in-hand. We want to
hear your Geode stories and best practices. Our call for proposals
 is now open and we
encourage you to submit a talk. To become inspired, see 2017 Geode @ S1P
highlights and presentations here
.

Don't hesitate, register today
 for SpringOne Platform and
take advantage of our early-bird prices. You can use the following discount
code to get an additional $100 off a conference pass: *Attendee_Geode_100*.

We look forward to you joining us this fall!

Regards
Jag

Re: [Discussion] Improving Spotless to be Even More Beautiful

[Patrick Rhomberg]

Glad to see a positive response!

@Galen, I had thought it already did that.

On Mon, Mar 19, 2018 at 4:52 PM, Galen O'Sullivan 
wrote:

> +1 to all of the above.
>
> Will Spotless also reorder imports according to our canonical ordering?
>
> On Mon, Mar 19, 2018 at 4:17 PM, Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> wrote:
>
> > +1
> >
> > On Mon, Mar 19, 2018 at 4:03 PM, Kirk Lund  wrote:
> >
> > > +1
> > >
> > > On Mon, Mar 19, 2018 at 2:51 PM, Patrick Rhomberg <
> prhomb...@pivotal.io>
> > > wrote:
> > >
> > > > Hello all!
> > > >
> > > >  I'm making another pass at patching up some of our smellier broken
> > > > windows, to mix metaphors.  To that end, there are a few things I'd
> > like
> > > to
> > > > add to spotless to more closely enforce adherence to our own style
> > guide.
> > > >
> > > > I'd like to do the following to our spotless:
> > > > - Bump spotless to the newest version, enabling some of the features
> > > below
> > > > - Have spotless only run spotless on files that have changed (Yay,
> > > slightly
> > > > faster builds!)
> > > > - Have spotless perform the following spotless tasks:
> > > > --- Remove unused imports.
> > > > --- Prohibit wildcard imports, which may require manual expansion by
> > the
> > > > developer.  (But, in fairness, you shouldn't be using wildcard
> imports
> > > > anyway.)
> > > > --- Remove trivial javadoc stubs that are implicit in the method
> > > signature
> > > > (e.g., "@param p" with no description of what p actually is).
> > > > --- Remove empty javadocs and block comments.
> > > >
> > > > This will again touch a great many files, so it should be targeted
> for
> > > > immediately following a release, perhaps the impending 1.5.  It can
> > > pretty
> > > > easily be exploded into several commits across each subproject and
> task
> > > for
> > > > ease of review.
> > > >
> > > > Thoughts?
> > > >
> > > > Imagination is Change.
> > > > ~Patrick Rhomberg
> > > >
> > >
> >
>

Re: [Discussion] Improving Spotless to be Even More Beautiful

[Bruce Schuchardt]

+1


On 3/19/18 2:51 PM, Patrick Rhomberg wrote:

Hello all!

  I'm making another pass at patching up some of our smellier broken
windows, to mix metaphors.  To that end, there are a few things I'd like to
add to spotless to more closely enforce adherence to our own style guide.

I'd like to do the following to our spotless:
- Bump spotless to the newest version, enabling some of the features below
- Have spotless only run spotless on files that have changed (Yay, slightly
faster builds!)
- Have spotless perform the following spotless tasks:
--- Remove unused imports.
--- Prohibit wildcard imports, which may require manual expansion by the
developer.  (But, in fairness, you shouldn't be using wildcard imports
anyway.)
--- Remove trivial javadoc stubs that are implicit in the method signature
(e.g., "@param p" with no description of what p actually is).
--- Remove empty javadocs and block comments.

This will again touch a great many files, so it should be targeted for
immediately following a release, perhaps the impending 1.5.  It can pretty
easily be exploded into several commits across each subproject and task for
ease of review.

Thoughts?

Imagination is Change.
~Patrick Rhomberg

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/212