Re: Release 1.8.0 pipeline issue

[Owen Nichols]

https://github.com/apache/geode/pull/2865 
 fixes this.  Patrick or Helena will 
take point on getting it reviewed and merged tomorrow.

> On Nov 15, 2018, at 2:08 PM, Jianxia Chen  wrote:
> 
> It sounds like we shouldn't have this job in the pipeline at all, since we
> only publish snapshots for the community on develop (and not release
> branches). I suggest you ignore it for now, and Patrick said he would look
> into deleting it properly tomorrow.
> 
> On Thu, Nov 15, 2018 at 10:47 AM Alexander Murmann 
> wrote:
> 
>> Hi community,
>> 
>> With the fix that Owen contributed the build on the 1.8.0 release pipeline
>> is passing. However, the PublishArtifacts job is failing with the below
>> error:
>> 
 Failed to publish publication 'maven' to repository 'maven'
>>> <
>> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-8-0-main/jobs/PublishArtifacts/builds/1#L5bea432b:881
>>> 
 Failed to deploy artifacts: Could not transfer artifact
>> org.apache.geode:geode-dunit:jar:1.8.0 from/to remote (
>> https://repository.apache.org/service/local/staging/deploy/maven2): Could
>> not write to resource
>> 'org/apache/geode/geode-dunit/1.8.0/geode-dunit-1.8.0.jar'
>>> 
>>> 
>> Is someone able to look at this who is more familiar with that particular
>> job?
>> 
>> Thanks!
>> 

Re: November 2018 Board Report Final Draft

[Mark Bretl]

Board report has been posted, thanks Robert!

--Mark

On Wed, Nov 14, 2018 at 10:00 AM Robert Houghton 
wrote:

> Here is the final form our report for the quarter. If it passes muster, can
> someone commit it to the Apache repository for me?
>
> ## Description:
> >
> > Apache Geode provides a database-like consistency model, reliable
> >> transaction
> >
> > processing and a shared-nothing architecture to maintain very low latency
> >
> > performance with high concurrency processing.
> >
> >
> >> ## Issues:
> >
> > There are no issues requiring board attention at this time.
> >
> >
> >> ## Activity:
> >
> > - We released v1.7.0, containing 859 commits resolving 196 bugs, 98
> >> improvements
> >
> >  and features, and a total of 357 JIRA tickets
> >
> > - We've made a number of build improvements, including upgrading to
> Gradle
> >> v4.10.1
> >
> > - We've begun testing with Java 11 and have added automated Windows
> >> testing to our CI jobs.
> >
> > - We have reviewed and acted on a number of code issues reported by
> >> lgtm.com .
> >
> > - We discussed use of Lombok and decided that adoption would prove to be
> a
> >> barrier to users and contributors.
> >
> > - We added a notifications@ mailing list to track GitHub PR activity.
> >
> > - We agreed to adopt a quarterly release schedule to improve
> >> predictability of releases.
> >
> > - We reorganized the top-level wiki for better navigation and
> >> discoverability.  We also added a page to track conference
> >
> >  presentations, blog postings, and other media.
> >
> > - The Geode Summit at SpringOnePlatform 2018 was very well-attended with
> >> over 400 people filling the conference room.
> >
> >  Both users and committers alike presented 15 talks during the
> >> conference.  The sessions were recorded and available on
> >
> >  youtube.
> >
> >
> >>
> >> ## Health report:
> >
> > - Overall project momentum is picking back up. We are seeing good results
> >> from the efforts
> >
> >  to improve test reliability
> >
> >
> >> ## PMC changes:
> >
> >
> >> - Currently 46 PMC members.
> >
> > - No new PMC members added in the last 3 months
> >
> > - Last PMC addition was Dick Cavender on Tue Feb 20 2018
> >
> >
> >
> > ## Committer base changes:
> >
> >
> >> - Currently 98 committers.
> >
> > - New commmitters:
> >
> >- Addison Huddy was added as a committer on Sat Sep 01 2018
> >
> >- Alexander Murmann was added as a committer on Sat Sep 08 2018
> >
> >- Blake Bender was added as a committer on Sat Sep 01 2018
> >
> >- Helena Bales was added as a committer on Sat Sep 01 2018
> >
> >- Ivan Godwin was added as a committer on Sat Sep 01 2018
> >
> >- Juan Ramos was added as a committer on Sat Sep 08 2018
> >
> >- Ryan McMahon was added as a committer on Sat Sep 01 2018
> >
> >- Michael Martell was added as a committer on Sat Sep 08 2018
> >
> >- Michael Oleske was added as a committer on Sat Sep 08 2018
> >
> >- Robert Houghton was added as a committer on Mon Oct 01 2018
> >
> >- Sean Goller was added as a committer on Sat Sep 01 2018
> >
> >
> >> ## Releases:
> >
> >
> >> - 1.7.0 was released on Thu Oct 04 2018
> >
> > - We have begun work on the 1.8.0 release.  We expect the release to
> >> include geode-native (a C++/C# client for Geode)
> >
> >  for the first time.
> >
> > - We're continuing to rotate release manager duties among committers to
> >> ensure the release process is well documented
> >
> >  and repeatable.
> >
> >
> >> ## Mailing list activity:
> >
> >
> >> - Mailing lists have remained active and have been seen a marked
> increase
> >> in use
> >
> >  for both development and issues
> >
> > - The increase in the user@ mailing list is very encouraging and seems
> to
> >> correlate with the Geode Summit.
> >
> >
> >> - dev@geode.apache.org:
> >
> >- 190 subscribers (up 8 in the last 3 months):
> >
> >- 889 emails sent to list (624 in previous quarter)
> >
> >
> >
> > - iss...@geode.apache.org:
> >
> >- 55 subscribers (up 1 in the last 3 months):
> >
> >- 4283 emails sent to list (2707 in previous quarter)
> >
> >
> >
> > - notificati...@geode.apache.org:
> >
> >- 7 subscribers (up 7 in the last 3 months):
> >
> >- 1998 emails sent to list (0 in previous quarter)
> >
> >
> >
> > - u...@geode.apache.org:
> >
> >- 249 subscribers (up 7 in the last 3 months):
> >
> >- 201 emails sent to list (138 in previous quarter)
> >
> >
> >
> >
> >
> > ## JIRA activity:
> >
> >
> >> - 456 JIRA tickets created in the last 3 months
> >
> > - 485 JIRA tickets closed/resolved in the last 3 months
> >
> >
> >>
>

Re: Release 1.8.0 pipeline issue

[Jianxia Chen]

It sounds like we shouldn't have this job in the pipeline at all, since we
only publish snapshots for the community on develop (and not release
branches). I suggest you ignore it for now, and Patrick said he would look
into deleting it properly tomorrow.

On Thu, Nov 15, 2018 at 10:47 AM Alexander Murmann 
wrote:

> Hi community,
>
> With the fix that Owen contributed the build on the 1.8.0 release pipeline
> is passing. However, the PublishArtifacts job is failing with the below
> error:
>
> > > Failed to publish publication 'maven' to repository 'maven'
> >  <
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-8-0-main/jobs/PublishArtifacts/builds/1#L5bea432b:881
> >
> >> Failed to deploy artifacts: Could not transfer artifact
> org.apache.geode:geode-dunit:jar:1.8.0 from/to remote (
> https://repository.apache.org/service/local/staging/deploy/maven2): Could
> not write to resource
> 'org/apache/geode/geode-dunit/1.8.0/geode-dunit-1.8.0.jar'
> >
> >
> Is someone able to look at this who is more familiar with that particular
> job?
>
> Thanks!
>

Re: [DISCUSS] - Create new repository for geode benchmarks

[Udo Kohlmeyer]

+1, never thought there was any other option...


On 11/15/18 10:47, Dan Smith wrote:

Hi all,

We (Naba, Sean, Brian and I) would like to add some benchmarks for geode,
with a goal of eventually running them as part of our concourse build and
detecting performance changes.

We think it makes sense to put these benchmarks in a separate
geode-benchmarks repository. That will make them less tightly coupled to a
specific revision of geode. What do you all think? If folks are okay with
this, I will go ahead and create the repository.

We have some prototype code in this repository with a simple client/server
put benchmark:  https://github.com/upthewaterspout/geode-performance.

-Dan

Re: [DISCUSS] - Create new repository for geode benchmarks

[Ryan McMahon]

+1 I think a separate repo makes sense, and I'm excited for this effort!


On Thu, Nov 15, 2018 at 10:47 AM Dan Smith  wrote:

> Hi all,
>
> We (Naba, Sean, Brian and I) would like to add some benchmarks for geode,
> with a goal of eventually running them as part of our concourse build and
> detecting performance changes.
>
> We think it makes sense to put these benchmarks in a separate
> geode-benchmarks repository. That will make them less tightly coupled to a
> specific revision of geode. What do you all think? If folks are okay with
> this, I will go ahead and create the repository.
>
> We have some prototype code in this repository with a simple client/server
> put benchmark:  https://github.com/upthewaterspout/geode-performance.
>
> -Dan
>

[DISCUSS] - Create new repository for geode benchmarks

[Dan Smith]

Hi all,

We (Naba, Sean, Brian and I) would like to add some benchmarks for geode,
with a goal of eventually running them as part of our concourse build and
detecting performance changes.

We think it makes sense to put these benchmarks in a separate
geode-benchmarks repository. That will make them less tightly coupled to a
specific revision of geode. What do you all think? If folks are okay with
this, I will go ahead and create the repository.

We have some prototype code in this repository with a simple client/server
put benchmark:  https://github.com/upthewaterspout/geode-performance.

-Dan

Release 1.8.0 pipeline issue

[Alexander Murmann]

Hi community,

With the fix that Owen contributed the build on the 1.8.0 release pipeline
is passing. However, the PublishArtifacts job is failing with the below
error:

> > Failed to publish publication 'maven' to repository 'maven'
>  
> 
>> Failed to deploy artifacts: Could not transfer artifact 
> org.apache.geode:geode-dunit:jar:1.8.0 from/to remote 
> (https://repository.apache.org/service/local/staging/deploy/maven2): Could 
> not write to resource 
> 'org/apache/geode/geode-dunit/1.8.0/geode-dunit-1.8.0.jar'
>
>
Is someone able to look at this who is more familiar with that particular
job?

Thanks!

Requesting access to concourse.

[Nabarun Nag]

Hi,

Please grant me access to the concourse infrastructure to run/setup
pipelines.

Regards
Nabarun Nag