Re: Next release: 1.4.0

[Anthony Baker]

I’ve updated the Jenkins nightly and release jobs.  Please ping me if you have 
any questions.

Anthony


> On Jan 5, 2018, at 10:00 AM, Anthony Baker  wrote:
> 
> +1
> 
> It should be pretty easy to clone the current pipeline for the 1.4.0 release 
> branch.
> 
> I’ll plan to update the Jenkins jobs to run the `build` and `updateArchives` 
> tasks since those still have value.
> 
> Anthony
> 

Re: Next release: 1.4.0

[Dan Smith]

I'm fine with switching off of Jenkins, we just need to be clear on what
our release criteria will be. It sounds like the new criteria being
proposed is that the concourse pipeline is passing for the release.

-Dan

On Thu, Jan 4, 2018 at 5:03 PM, Alexander Murmann 
wrote:

> The Concourse pipeline seems much more reliable at this point and the
> pipelines should be providing equivalent test coverage. Given that, are
> there any reasons to not deprecate Jenkins?
>
> On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:
>
> > Hi Swapnil,
> >
> > GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should be
> > fixed because the process.ClusterConfigurationNotAvailableException
> should
> > probably be reinstated.  If others don't think it's needed then feel free
> > to remove the fix tag.
> >
> > -Jason
> >
> > On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
> >
> > > Our process up to this point has been to not ship until the jenkins
> > builds
> > > on the release branch pass. We've been experimenting with concourse in
> > > parallel with jenkins, but the jenkins builds on develop at least are
> > still
> > > pretty messy. How are we going to ship this release? Should both be
> > > passing?
> > >
> > > -Dan
> > >
> > > On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar  >
> > > wrote:
> > >
> > > > Since all the issues tagged for 1.4.0 release
> > > >  > > > rapidView=92=GEODE=planning=
> > > > GEODE-3688=visible=12341842>
> > > > have been addressed, I went ahead and created a release branch for
> > 1.4.0.
> > > >
> > > > Can someone please update the concourse pipelines to pick up this
> > release
> > > > branch?
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <
> sbawas...@pivotal.io
> > >
> > > > wrote:
> > > >
> > > > > Well, making sure that the JIRA's status is up-to-date and removing
> > the
> > > > > 1.4.0 version tag if the fix can wait for a later release.
> > > > >
> > > > > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
> > > > mdo...@pivotal.io>
> > > > > wrote:
> > > > >
> > > > >> What sort of update? I know that GEODE-4010 has a PR that's
> awaiting
> > > > >> review and merge.
> > > > >>
> > > > >> Sarge
> > > > >>
> > > > >> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar <
> sbawas...@pivotal.io
> > >
> > > > >> wrote:
> > > > >> >
> > > > >> > I would like to volunteer as a release manager.
> > > > >> > Currently there are 14 issues that are marked for 1.4.0. If you
> > are
> > > > >> working
> > > > >> > on any of these, can you please update the JIRA?
> > > > >> >
> > > > >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > > > rapidView=92=GEODE=planning=
> > > > GEODE-3688=visible=12341842
> > > > >> >
> > > > >> > Thanks!
> > > > >> >
> > > > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker <
> aba...@pivotal.io>
> > > > >> wrote:
> > > > >> >
> > > > >> >> Bump.  Any volunteers?  If not, I’ll do this.
> > > > >> >>
> > > > >> >> Anthony
> > > > >> >>
> > > > >> >>
> > > > >> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker  >
> > > > wrote:
> > > > >> >>>
> > > > >> >>> We released Geode 1.3.0 at the end of October.  Our next
> release
> > > > will
> > > > >> be
> > > > >> >> 1.4.0.  Questions:
> > > > >> >>>
> > > > >> >>> 1) Who wants to volunteer as a release manager?
> > > > >> >>> 2) What do we want to include in the release?
> > > > >> >>> 3) When do we want to do this?
> > > > >> >>>
> > > > >> >>> IMO, let's should shoot for an early Dec release.
> > > > >> >>>
> > > > >> >>> Anthony
> > > > >> >>>
> > > > >> >>
> > > > >> >>
> > > > >>
> > > > >>
> > > >
> > >
> >
>

Re: Next release: 1.4.0

[Bruce Schuchardt]

I need to merge feature/GEODE-4192 to the release branch.  There is a 
Protobuf client/locator change that needs to be included in the release.



On 1/5/18 11:15 AM, Sean Goller wrote:

The release pipeline is up:
https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.4.0

-Sean.

On Fri, Jan 5, 2018 at 10:00 AM, Anthony Baker  wrote:


+1

It should be pretty easy to clone the current pipeline for the 1.4.0
release branch.

I’ll plan to update the Jenkins jobs to run the `build` and
`updateArchives` tasks since those still have value.

Anthony



On Jan 4, 2018, at 5:03 PM, Alexander Murmann 

wrote:

The Concourse pipeline seems much more reliable at this point and the
pipelines should be providing equivalent test coverage. Given that, are
there any reasons to not deprecate Jenkins?

On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:


Hi Swapnil,

GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should

be

fixed because the process.ClusterConfigurationNotAvailableException

should

probably be reinstated.  If others don't think it's needed then feel

free

to remove the fix tag.

-Jason

On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:


Our process up to this point has been to not ship until the jenkins

builds

on the release branch pass. We've been experimenting with concourse in
parallel with jenkins, but the jenkins builds on develop at least are

still

pretty messy. How are we going to ship this release? Should both be
passing?

-Dan

On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar 
have been addressed, I went ahead and created a release branch for

1.4.0.

Can someone please update the concourse pipelines to pick up this

release

branch?

Thanks!


On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <

sbawas...@pivotal.io

wrote:


Well, making sure that the JIRA's status is up-to-date and removing

the

1.4.0 version tag if the fix can wait for a later release.

On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <

mdo...@pivotal.io>

wrote:


What sort of update? I know that GEODE-4010 has a PR that's awaiting
review and merge.

Sarge


On 28 Nov, 2017, at 10:03, Swapnil Bawaskar 

wrote:

Bump.  Any volunteers?  If not, I’ll do this.

Anthony



On Nov 22, 2017, at 1:48 PM, Anthony Baker 

wrote:

We released Geode 1.3.0 at the end of October.  Our next release

will

be

1.4.0.  Questions:

1) Who wants to volunteer as a release manager?
2) What do we want to include in the release?
3) When do we want to do this?

IMO, let's should shoot for an early Dec release.

Anthony

Re: Next release: 1.4.0

[Sean Goller]

The release pipeline is up:
https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.4.0

-Sean.

On Fri, Jan 5, 2018 at 10:00 AM, Anthony Baker  wrote:

> +1
>
> It should be pretty easy to clone the current pipeline for the 1.4.0
> release branch.
>
> I’ll plan to update the Jenkins jobs to run the `build` and
> `updateArchives` tasks since those still have value.
>
> Anthony
>
>
> > On Jan 4, 2018, at 5:03 PM, Alexander Murmann 
> wrote:
> >
> > The Concourse pipeline seems much more reliable at this point and the
> > pipelines should be providing equivalent test coverage. Given that, are
> > there any reasons to not deprecate Jenkins?
> >
> > On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:
> >
> >> Hi Swapnil,
> >>
> >> GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should
> be
> >> fixed because the process.ClusterConfigurationNotAvailableException
> should
> >> probably be reinstated.  If others don't think it's needed then feel
> free
> >> to remove the fix tag.
> >>
> >> -Jason
> >>
> >> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
> >>
> >>> Our process up to this point has been to not ship until the jenkins
> >> builds
> >>> on the release branch pass. We've been experimenting with concourse in
> >>> parallel with jenkins, but the jenkins builds on develop at least are
> >> still
> >>> pretty messy. How are we going to ship this release? Should both be
> >>> passing?
> >>>
> >>> -Dan
> >>>
> >>> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar  >
> >>> wrote:
> >>>
>  Since all the issues tagged for 1.4.0 release
>    rapidView=92=GEODE=planning=
>  GEODE-3688=visible=12341842>
>  have been addressed, I went ahead and created a release branch for
> >> 1.4.0.
> 
>  Can someone please update the concourse pipelines to pick up this
> >> release
>  branch?
> 
>  Thanks!
> 
> 
>  On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <
> sbawas...@pivotal.io
> >>>
>  wrote:
> 
> > Well, making sure that the JIRA's status is up-to-date and removing
> >> the
> > 1.4.0 version tag if the fix can wait for a later release.
> >
> > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
>  mdo...@pivotal.io>
> > wrote:
> >
> >> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> >> review and merge.
> >>
> >> Sarge
> >>
> >>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar  >>>
> >> wrote:
> >>>
> >>> I would like to volunteer as a release manager.
> >>> Currently there are 14 issues that are marked for 1.4.0. If you
> >> are
> >> working
> >>> on any of these, can you please update the JIRA?
> >>>
> >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
>  rapidView=92=GEODE=planning=
>  GEODE-3688=visible=12341842
> >>>
> >>> Thanks!
> >>>
> >>> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
> >> wrote:
> >>>
>  Bump.  Any volunteers?  If not, I’ll do this.
> 
>  Anthony
> 
> 
> > On Nov 22, 2017, at 1:48 PM, Anthony Baker 
>  wrote:
> >
> > We released Geode 1.3.0 at the end of October.  Our next release
>  will
> >> be
>  1.4.0.  Questions:
> >
> > 1) Who wants to volunteer as a release manager?
> > 2) What do we want to include in the release?
> > 3) When do we want to do this?
> >
> > IMO, let's should shoot for an early Dec release.
> >
> > Anthony
> >
> 
> 
> >>
> >>
> 
> >>>
> >>
>
>

Re: Next release: 1.4.0

[Jason Huynh]

Hi Anil,

Thanks, I'll take a look at that, I added that test a little while ago..

On Fri, Jan 5, 2018 at 10:13 AM Anilkumar Gingade 
wrote:

> I see :rat failing on Jenkins...
>
> The last run: https://builds.apache.org/job/Geode-release/100/console
>
> All test reports at
> /home/jenkins/jenkins-slave/workspace/Geode-release/build/reports/combined
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':rat'.
> > Found 1 files with unapproved/unknown licenses. See
> file:/home/jenkins/jenkins-slave/workspace/Geode-release/build/reports/rat/rat-report.txt
>
> *** Error:
>
> Unapproved licenses:
>
> /home/jenkins/jenkins-slave/workspace/Geode-release/geode-core/src/test/resources/org/apache/geode/cache/execute/FunctionAdapterJUnitTest.serializedFunctionAdapterWithDifferentSerialVersionUID
>
>
> -Anil.
>
>
>
> On Fri, Jan 5, 2018 at 10:00 AM, Anthony Baker  wrote:
>
> > +1
> >
> > It should be pretty easy to clone the current pipeline for the 1.4.0
> > release branch.
> >
> > I’ll plan to update the Jenkins jobs to run the `build` and
> > `updateArchives` tasks since those still have value.
> >
> > Anthony
> >
> >
> > > On Jan 4, 2018, at 5:03 PM, Alexander Murmann 
> > wrote:
> > >
> > > The Concourse pipeline seems much more reliable at this point and the
> > > pipelines should be providing equivalent test coverage. Given that, are
> > > there any reasons to not deprecate Jenkins?
> > >
> > > On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:
> > >
> > >> Hi Swapnil,
> > >>
> > >> GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should
> > be
> > >> fixed because the process.ClusterConfigurationNotAvailableException
> > should
> > >> probably be reinstated.  If others don't think it's needed then feel
> > free
> > >> to remove the fix tag.
> > >>
> > >> -Jason
> > >>
> > >> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
> > >>
> > >>> Our process up to this point has been to not ship until the jenkins
> > >> builds
> > >>> on the release branch pass. We've been experimenting with concourse
> in
> > >>> parallel with jenkins, but the jenkins builds on develop at least are
> > >> still
> > >>> pretty messy. How are we going to ship this release? Should both be
> > >>> passing?
> > >>>
> > >>> -Dan
> > >>>
> > >>> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar <
> sbawas...@pivotal.io
> > >
> > >>> wrote:
> > >>>
> >  Since all the issues tagged for 1.4.0 release
> >   >  rapidView=92=GEODE=planning=
> >  GEODE-3688=visible=12341842>
> >  have been addressed, I went ahead and created a release branch for
> > >> 1.4.0.
> > 
> >  Can someone please update the concourse pipelines to pick up this
> > >> release
> >  branch?
> > 
> >  Thanks!
> > 
> > 
> >  On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <
> > sbawas...@pivotal.io
> > >>>
> >  wrote:
> > 
> > > Well, making sure that the JIRA's status is up-to-date and removing
> > >> the
> > > 1.4.0 version tag if the fix can wait for a later release.
> > >
> > > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
> >  mdo...@pivotal.io>
> > > wrote:
> > >
> > >> What sort of update? I know that GEODE-4010 has a PR that's
> awaiting
> > >> review and merge.
> > >>
> > >> Sarge
> > >>
> > >>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar <
> sbawas...@pivotal.io
> > >>>
> > >> wrote:
> > >>>
> > >>> I would like to volunteer as a release manager.
> > >>> Currently there are 14 issues that are marked for 1.4.0. If you
> > >> are
> > >> working
> > >>> on any of these, can you please update the JIRA?
> > >>>
> > >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
> >  rapidView=92=GEODE=planning=
> >  GEODE-3688=visible=12341842
> > >>>
> > >>> Thanks!
> > >>>
> > >>> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker  >
> > >> wrote:
> > >>>
> >  Bump.  Any volunteers?  If not, I’ll do this.
> > 
> >  Anthony
> > 
> > 
> > > On Nov 22, 2017, at 1:48 PM, Anthony Baker 
> >  wrote:
> > >
> > > We released Geode 1.3.0 at the end of October.  Our next
> release
> >  will
> > >> be
> >  1.4.0.  Questions:
> > >
> > > 1) Who wants to volunteer as a release manager?
> > > 2) What do we want to include in the release?
> > > 3) When do we want to do this?
> > >
> > > IMO, let's should shoot for an early Dec release.
> > >
> > > Anthony
> > >
> > 
> > 
> > >>
> > >>
> > 
> > >>>
> > >>
> >
> >
>

Re: Next release: 1.4.0

[Anilkumar Gingade]

I see :rat failing on Jenkins...

The last run: https://builds.apache.org/job/Geode-release/100/console

All test reports at
/home/jenkins/jenkins-slave/workspace/Geode-release/build/reports/combined

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':rat'.
> Found 1 files with unapproved/unknown licenses. See 
> file:/home/jenkins/jenkins-slave/workspace/Geode-release/build/reports/rat/rat-report.txt

*** Error:

Unapproved licenses:
  
/home/jenkins/jenkins-slave/workspace/Geode-release/geode-core/src/test/resources/org/apache/geode/cache/execute/FunctionAdapterJUnitTest.serializedFunctionAdapterWithDifferentSerialVersionUID


-Anil.



On Fri, Jan 5, 2018 at 10:00 AM, Anthony Baker  wrote:

> +1
>
> It should be pretty easy to clone the current pipeline for the 1.4.0
> release branch.
>
> I’ll plan to update the Jenkins jobs to run the `build` and
> `updateArchives` tasks since those still have value.
>
> Anthony
>
>
> > On Jan 4, 2018, at 5:03 PM, Alexander Murmann 
> wrote:
> >
> > The Concourse pipeline seems much more reliable at this point and the
> > pipelines should be providing equivalent test coverage. Given that, are
> > there any reasons to not deprecate Jenkins?
> >
> > On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:
> >
> >> Hi Swapnil,
> >>
> >> GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should
> be
> >> fixed because the process.ClusterConfigurationNotAvailableException
> should
> >> probably be reinstated.  If others don't think it's needed then feel
> free
> >> to remove the fix tag.
> >>
> >> -Jason
> >>
> >> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
> >>
> >>> Our process up to this point has been to not ship until the jenkins
> >> builds
> >>> on the release branch pass. We've been experimenting with concourse in
> >>> parallel with jenkins, but the jenkins builds on develop at least are
> >> still
> >>> pretty messy. How are we going to ship this release? Should both be
> >>> passing?
> >>>
> >>> -Dan
> >>>
> >>> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar  >
> >>> wrote:
> >>>
>  Since all the issues tagged for 1.4.0 release
>    rapidView=92=GEODE=planning=
>  GEODE-3688=visible=12341842>
>  have been addressed, I went ahead and created a release branch for
> >> 1.4.0.
> 
>  Can someone please update the concourse pipelines to pick up this
> >> release
>  branch?
> 
>  Thanks!
> 
> 
>  On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar <
> sbawas...@pivotal.io
> >>>
>  wrote:
> 
> > Well, making sure that the JIRA's status is up-to-date and removing
> >> the
> > 1.4.0 version tag if the fix can wait for a later release.
> >
> > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
>  mdo...@pivotal.io>
> > wrote:
> >
> >> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> >> review and merge.
> >>
> >> Sarge
> >>
> >>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar  >>>
> >> wrote:
> >>>
> >>> I would like to volunteer as a release manager.
> >>> Currently there are 14 issues that are marked for 1.4.0. If you
> >> are
> >> working
> >>> on any of these, can you please update the JIRA?
> >>>
> >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
>  rapidView=92=GEODE=planning=
>  GEODE-3688=visible=12341842
> >>>
> >>> Thanks!
> >>>
> >>> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
> >> wrote:
> >>>
>  Bump.  Any volunteers?  If not, I’ll do this.
> 
>  Anthony
> 
> 
> > On Nov 22, 2017, at 1:48 PM, Anthony Baker 
>  wrote:
> >
> > We released Geode 1.3.0 at the end of October.  Our next release
>  will
> >> be
>  1.4.0.  Questions:
> >
> > 1) Who wants to volunteer as a release manager?
> > 2) What do we want to include in the release?
> > 3) When do we want to do this?
> >
> > IMO, let's should shoot for an early Dec release.
> >
> > Anthony
> >
> 
> 
> >>
> >>
> 
> >>>
> >>
>
>

Re: Next release: 1.4.0

[Anthony Baker]

+1

It should be pretty easy to clone the current pipeline for the 1.4.0 release 
branch.

I’ll plan to update the Jenkins jobs to run the `build` and `updateArchives` 
tasks since those still have value.

Anthony


> On Jan 4, 2018, at 5:03 PM, Alexander Murmann  wrote:
> 
> The Concourse pipeline seems much more reliable at this point and the
> pipelines should be providing equivalent test coverage. Given that, are
> there any reasons to not deprecate Jenkins?
> 
> On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:
> 
>> Hi Swapnil,
>> 
>> GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should be
>> fixed because the process.ClusterConfigurationNotAvailableException should
>> probably be reinstated.  If others don't think it's needed then feel free
>> to remove the fix tag.
>> 
>> -Jason
>> 
>> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
>> 
>>> Our process up to this point has been to not ship until the jenkins
>> builds
>>> on the release branch pass. We've been experimenting with concourse in
>>> parallel with jenkins, but the jenkins builds on develop at least are
>> still
>>> pretty messy. How are we going to ship this release? Should both be
>>> passing?
>>> 
>>> -Dan
>>> 
>>> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar 
>>> wrote:
>>> 
 Since all the issues tagged for 1.4.0 release
 
 have been addressed, I went ahead and created a release branch for
>> 1.4.0.
 
 Can someone please update the concourse pipelines to pick up this
>> release
 branch?
 
 Thanks!
 
 
 On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar >> 
 wrote:
 
> Well, making sure that the JIRA's status is up-to-date and removing
>> the
> 1.4.0 version tag if the fix can wait for a later release.
> 
> On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
 mdo...@pivotal.io>
> wrote:
> 
>> What sort of update? I know that GEODE-4010 has a PR that's awaiting
>> review and merge.
>> 
>> Sarge
>> 
>>> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar >> 
>> wrote:
>>> 
>>> I would like to volunteer as a release manager.
>>> Currently there are 14 issues that are marked for 1.4.0. If you
>> are
>> working
>>> on any of these, can you please update the JIRA?
>>> 
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?
 rapidView=92=GEODE=planning=
 GEODE-3688=visible=12341842
>>> 
>>> Thanks!
>>> 
>>> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
>> wrote:
>>> 
 Bump.  Any volunteers?  If not, I’ll do this.
 
 Anthony
 
 
> On Nov 22, 2017, at 1:48 PM, Anthony Baker 
 wrote:
> 
> We released Geode 1.3.0 at the end of October.  Our next release
 will
>> be
 1.4.0.  Questions:
> 
> 1) Who wants to volunteer as a release manager?
> 2) What do we want to include in the release?
> 3) When do we want to do this?
> 
> IMO, let's should shoot for an early Dec release.
> 
> Anthony
> 
 
 
>> 
>> 
 
>>> 
>> 

Re: Next release: 1.4.0

[Alexander Murmann]

The Concourse pipeline seems much more reliable at this point and the
pipelines should be providing equivalent test coverage. Given that, are
there any reasons to not deprecate Jenkins?

On Thu, Jan 4, 2018 at 4:55 PM, Jason Huynh  wrote:

> Hi Swapnil,
>
> GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should be
> fixed because the process.ClusterConfigurationNotAvailableException should
> probably be reinstated.  If others don't think it's needed then feel free
> to remove the fix tag.
>
> -Jason
>
> On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:
>
> > Our process up to this point has been to not ship until the jenkins
> builds
> > on the release branch pass. We've been experimenting with concourse in
> > parallel with jenkins, but the jenkins builds on develop at least are
> still
> > pretty messy. How are we going to ship this release? Should both be
> > passing?
> >
> > -Dan
> >
> > On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar 
> > wrote:
> >
> > > Since all the issues tagged for 1.4.0 release
> > >  > > rapidView=92=GEODE=planning=
> > > GEODE-3688=visible=12341842>
> > > have been addressed, I went ahead and created a release branch for
> 1.4.0.
> > >
> > > Can someone please update the concourse pipelines to pick up this
> release
> > > branch?
> > >
> > > Thanks!
> > >
> > >
> > > On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar  >
> > > wrote:
> > >
> > > > Well, making sure that the JIRA's status is up-to-date and removing
> the
> > > > 1.4.0 version tag if the fix can wait for a later release.
> > > >
> > > > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
> > > mdo...@pivotal.io>
> > > > wrote:
> > > >
> > > >> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> > > >> review and merge.
> > > >>
> > > >> Sarge
> > > >>
> > > >> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar  >
> > > >> wrote:
> > > >> >
> > > >> > I would like to volunteer as a release manager.
> > > >> > Currently there are 14 issues that are marked for 1.4.0. If you
> are
> > > >> working
> > > >> > on any of these, can you please update the JIRA?
> > > >> >
> > > >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > > rapidView=92=GEODE=planning=
> > > GEODE-3688=visible=12341842
> > > >> >
> > > >> > Thanks!
> > > >> >
> > > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
> > > >> wrote:
> > > >> >
> > > >> >> Bump.  Any volunteers?  If not, I’ll do this.
> > > >> >>
> > > >> >> Anthony
> > > >> >>
> > > >> >>
> > > >> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker 
> > > wrote:
> > > >> >>>
> > > >> >>> We released Geode 1.3.0 at the end of October.  Our next release
> > > will
> > > >> be
> > > >> >> 1.4.0.  Questions:
> > > >> >>>
> > > >> >>> 1) Who wants to volunteer as a release manager?
> > > >> >>> 2) What do we want to include in the release?
> > > >> >>> 3) When do we want to do this?
> > > >> >>>
> > > >> >>> IMO, let's should shoot for an early Dec release.
> > > >> >>>
> > > >> >>> Anthony
> > > >> >>>
> > > >> >>
> > > >> >>
> > > >>
> > > >>
> > >
> >
>

Re: Next release: 1.4.0

[Jason Huynh]

Hi Swapnil,

GEODE-4140 was just marked for 1.4.  I think part of GEODE-4140 should be
fixed because the process.ClusterConfigurationNotAvailableException should
probably be reinstated.  If others don't think it's needed then feel free
to remove the fix tag.

-Jason

On Thu, Jan 4, 2018 at 4:38 PM Dan Smith  wrote:

> Our process up to this point has been to not ship until the jenkins builds
> on the release branch pass. We've been experimenting with concourse in
> parallel with jenkins, but the jenkins builds on develop at least are still
> pretty messy. How are we going to ship this release? Should both be
> passing?
>
> -Dan
>
> On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar 
> wrote:
>
> > Since all the issues tagged for 1.4.0 release
> >  > rapidView=92=GEODE=planning=
> > GEODE-3688=visible=12341842>
> > have been addressed, I went ahead and created a release branch for 1.4.0.
> >
> > Can someone please update the concourse pipelines to pick up this release
> > branch?
> >
> > Thanks!
> >
> >
> > On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar 
> > wrote:
> >
> > > Well, making sure that the JIRA's status is up-to-date and removing the
> > > 1.4.0 version tag if the fix can wait for a later release.
> > >
> > > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
> > mdo...@pivotal.io>
> > > wrote:
> > >
> > >> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> > >> review and merge.
> > >>
> > >> Sarge
> > >>
> > >> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar 
> > >> wrote:
> > >> >
> > >> > I would like to volunteer as a release manager.
> > >> > Currently there are 14 issues that are marked for 1.4.0. If you are
> > >> working
> > >> > on any of these, can you please update the JIRA?
> > >> >
> > >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > rapidView=92=GEODE=planning=
> > GEODE-3688=visible=12341842
> > >> >
> > >> > Thanks!
> > >> >
> > >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
> > >> wrote:
> > >> >
> > >> >> Bump.  Any volunteers?  If not, I’ll do this.
> > >> >>
> > >> >> Anthony
> > >> >>
> > >> >>
> > >> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker 
> > wrote:
> > >> >>>
> > >> >>> We released Geode 1.3.0 at the end of October.  Our next release
> > will
> > >> be
> > >> >> 1.4.0.  Questions:
> > >> >>>
> > >> >>> 1) Who wants to volunteer as a release manager?
> > >> >>> 2) What do we want to include in the release?
> > >> >>> 3) When do we want to do this?
> > >> >>>
> > >> >>> IMO, let's should shoot for an early Dec release.
> > >> >>>
> > >> >>> Anthony
> > >> >>>
> > >> >>
> > >> >>
> > >>
> > >>
> >
>

Re: Next release: 1.4.0

[Dan Smith]

Our process up to this point has been to not ship until the jenkins builds
on the release branch pass. We've been experimenting with concourse in
parallel with jenkins, but the jenkins builds on develop at least are still
pretty messy. How are we going to ship this release? Should both be passing?

-Dan

On Thu, Jan 4, 2018 at 4:23 PM, Swapnil Bawaskar 
wrote:

> Since all the issues tagged for 1.4.0 release
>  rapidView=92=GEODE=planning=
> GEODE-3688=visible=12341842>
> have been addressed, I went ahead and created a release branch for 1.4.0.
>
> Can someone please update the concourse pipelines to pick up this release
> branch?
>
> Thanks!
>
>
> On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar 
> wrote:
>
> > Well, making sure that the JIRA's status is up-to-date and removing the
> > 1.4.0 version tag if the fix can wait for a later release.
> >
> > On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge <
> mdo...@pivotal.io>
> > wrote:
> >
> >> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> >> review and merge.
> >>
> >> Sarge
> >>
> >> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar 
> >> wrote:
> >> >
> >> > I would like to volunteer as a release manager.
> >> > Currently there are 14 issues that are marked for 1.4.0. If you are
> >> working
> >> > on any of these, can you please update the JIRA?
> >> >
> >> https://issues.apache.org/jira/secure/RapidBoard.jspa?
> rapidView=92=GEODE=planning=
> GEODE-3688=visible=12341842
> >> >
> >> > Thanks!
> >> >
> >> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
> >> wrote:
> >> >
> >> >> Bump.  Any volunteers?  If not, I’ll do this.
> >> >>
> >> >> Anthony
> >> >>
> >> >>
> >> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker 
> wrote:
> >> >>>
> >> >>> We released Geode 1.3.0 at the end of October.  Our next release
> will
> >> be
> >> >> 1.4.0.  Questions:
> >> >>>
> >> >>> 1) Who wants to volunteer as a release manager?
> >> >>> 2) What do we want to include in the release?
> >> >>> 3) When do we want to do this?
> >> >>>
> >> >>> IMO, let's should shoot for an early Dec release.
> >> >>>
> >> >>> Anthony
> >> >>>
> >> >>
> >> >>
> >>
> >>
>

Re: Next release: 1.4.0

[Swapnil Bawaskar]

Since all the issues tagged for 1.4.0 release

have been addressed, I went ahead and created a release branch for 1.4.0.

Can someone please update the concourse pipelines to pick up this release
branch?

Thanks!


On Tue, Nov 28, 2017 at 1:58 PM Swapnil Bawaskar 
wrote:

> Well, making sure that the JIRA's status is up-to-date and removing the
> 1.4.0 version tag if the fix can wait for a later release.
>
> On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge 
> wrote:
>
>> What sort of update? I know that GEODE-4010 has a PR that's awaiting
>> review and merge.
>>
>> Sarge
>>
>> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar 
>> wrote:
>> >
>> > I would like to volunteer as a release manager.
>> > Currently there are 14 issues that are marked for 1.4.0. If you are
>> working
>> > on any of these, can you please update the JIRA?
>> >
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92=GEODE=planning=GEODE-3688=visible=12341842
>> >
>> > Thanks!
>> >
>> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker 
>> wrote:
>> >
>> >> Bump.  Any volunteers?  If not, I’ll do this.
>> >>
>> >> Anthony
>> >>
>> >>
>> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker  wrote:
>> >>>
>> >>> We released Geode 1.3.0 at the end of October.  Our next release will
>> be
>> >> 1.4.0.  Questions:
>> >>>
>> >>> 1) Who wants to volunteer as a release manager?
>> >>> 2) What do we want to include in the release?
>> >>> 3) When do we want to do this?
>> >>>
>> >>> IMO, let's should shoot for an early Dec release.
>> >>>
>> >>> Anthony
>> >>>
>> >>
>> >>
>>
>>

Re: Next release: 1.4.0

[Swapnil Bawaskar]

Well, making sure that the JIRA's status is up-to-date and removing the
1.4.0 version tag if the fix can wait for a later release.

On Tue, Nov 28, 2017 at 12:22 PM Michael William Dodge 
wrote:

> What sort of update? I know that GEODE-4010 has a PR that's awaiting
> review and merge.
>
> Sarge
>
> > On 28 Nov, 2017, at 10:03, Swapnil Bawaskar 
> wrote:
> >
> > I would like to volunteer as a release manager.
> > Currently there are 14 issues that are marked for 1.4.0. If you are
> working
> > on any of these, can you please update the JIRA?
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92=GEODE=planning=GEODE-3688=visible=12341842
> >
> > Thanks!
> >
> > On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker  wrote:
> >
> >> Bump.  Any volunteers?  If not, I’ll do this.
> >>
> >> Anthony
> >>
> >>
> >>> On Nov 22, 2017, at 1:48 PM, Anthony Baker  wrote:
> >>>
> >>> We released Geode 1.3.0 at the end of October.  Our next release will
> be
> >> 1.4.0.  Questions:
> >>>
> >>> 1) Who wants to volunteer as a release manager?
> >>> 2) What do we want to include in the release?
> >>> 3) When do we want to do this?
> >>>
> >>> IMO, let's should shoot for an early Dec release.
> >>>
> >>> Anthony
> >>>
> >>
> >>
>
>

Re: Next release: 1.4.0

[Michael William Dodge]

What sort of update? I know that GEODE-4010 has a PR that's awaiting review and 
merge.

Sarge

> On 28 Nov, 2017, at 10:03, Swapnil Bawaskar  wrote:
> 
> I would like to volunteer as a release manager.
> Currently there are 14 issues that are marked for 1.4.0. If you are working
> on any of these, can you please update the JIRA?
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92=GEODE=planning=GEODE-3688=visible=12341842
> 
> Thanks!
> 
> On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker  wrote:
> 
>> Bump.  Any volunteers?  If not, I’ll do this.
>> 
>> Anthony
>> 
>> 
>>> On Nov 22, 2017, at 1:48 PM, Anthony Baker  wrote:
>>> 
>>> We released Geode 1.3.0 at the end of October.  Our next release will be
>> 1.4.0.  Questions:
>>> 
>>> 1) Who wants to volunteer as a release manager?
>>> 2) What do we want to include in the release?
>>> 3) When do we want to do this?
>>> 
>>> IMO, let's should shoot for an early Dec release.
>>> 
>>> Anthony
>>> 
>> 
>> 

Re: Next release: 1.4.0

[Swapnil Bawaskar]

I would like to volunteer as a release manager.
Currently there are 14 issues that are marked for 1.4.0. If you are working
on any of these, can you please update the JIRA?
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92=GEODE=planning=GEODE-3688=visible=12341842

Thanks!

On Tue, Nov 28, 2017 at 9:42 AM Anthony Baker  wrote:

> Bump.  Any volunteers?  If not, I’ll do this.
>
> Anthony
>
>
> > On Nov 22, 2017, at 1:48 PM, Anthony Baker  wrote:
> >
> > We released Geode 1.3.0 at the end of October.  Our next release will be
> 1.4.0.  Questions:
> >
> > 1) Who wants to volunteer as a release manager?
> > 2) What do we want to include in the release?
> > 3) When do we want to do this?
> >
> > IMO, let's should shoot for an early Dec release.
> >
> > Anthony
> >
>
>

Re: Next release: 1.4.0

[Anthony Baker]

Bump.  Any volunteers?  If not, I’ll do this.

Anthony


> On Nov 22, 2017, at 1:48 PM, Anthony Baker  wrote:
> 
> We released Geode 1.3.0 at the end of October.  Our next release will be 
> 1.4.0.  Questions:
> 
> 1) Who wants to volunteer as a release manager?
> 2) What do we want to include in the release?
> 3) When do we want to do this?
> 
> IMO, let's should shoot for an early Dec release.
> 
> Anthony
> 

Re: Next release: 1.4.0

[Michael Stolz]

I'd like to see it include the recently completed work on indexing nested
objects in the Apache Lucene integration.
Early Dec sounds good to me.

--
Mike Stolz


On Wed, Nov 22, 2017 at 4:48 PM, Anthony Baker  wrote:

> We released Geode 1.3.0 at the end of October.  Our next release will be
> 1.4.0.  Questions:
>
> 1) Who wants to volunteer as a release manager?
> 2) What do we want to include in the release?
> 3) When do we want to do this?
>
> IMO, let's should shoot for an early Dec release.
>
> Anthony
>
>