Odg: Next release

[Mario Kevo]

Thanks for the info!

BR,
Mario

Šalje: Ernest Burghardt 
Poslano: 17. ožujka 2020. 0:06
Prima: dev@geode.apache.org 
Predmet: Re: Next release

Hi Mario,

There is still some work to be done to ensure performance is on par with
previous releases... here are a few tickets related to the efforts

https://issues.apache.org/jira/browse/GEODE-7763
https://issues.apache.org/jira/browse/GEODE-7832
https://issues.apache.org/jira/browse/GEODE-7853
https://issues.apache.org/jira/browse/GEODE-7863
https://issues.apache.org/jira/browse/GEODE-6154

Best regards,
EB

On Mon, Mar 16, 2020 at 2:03 AM Mario Kevo  wrote:

> Hi geode-dev,
>
> When we will have Apache Geode 1.12.0 release?
> I saw that all test passed and the last commit was before 4 days(typos
> correct).
> Are we waiting fix for some critical issue or something else?
>
> Thanks and BR,
> Mario
>

Re: Next release

[Ernest Burghardt]

Hi Mario,

There is still some work to be done to ensure performance is on par with
previous releases... here are a few tickets related to the efforts

https://issues.apache.org/jira/browse/GEODE-7763
https://issues.apache.org/jira/browse/GEODE-7832
https://issues.apache.org/jira/browse/GEODE-7853
https://issues.apache.org/jira/browse/GEODE-7863
https://issues.apache.org/jira/browse/GEODE-6154

Best regards,
EB

On Mon, Mar 16, 2020 at 2:03 AM Mario Kevo  wrote:

> Hi geode-dev,
>
> When we will have Apache Geode 1.12.0 release?
> I saw that all test passed and the last commit was before 4 days(typos
> correct).
> Are we waiting fix for some critical issue or something else?
>
> Thanks and BR,
> Mario
>

Next release

[Mario Kevo]

Hi geode-dev,

When we will have Apache Geode 1.12.0 release?
I saw that all test passed and the last commit was before 4 days(typos correct).
Are we waiting fix for some critical issue or something else?

Thanks and BR,
Mario

Re: Next release 1.7.0

[Barbara Pruijn]

Great! Thank you!

Barbara

> On May 18, 2018, at 12:18 PM, Nabarun Nag  wrote:
> 
> Hi Barbara,
> 
> I volunteer to be the release manager for Apache Geode 1.7.0.
> 
> Regards
> Naba
> 
> 
> On Fri, May 18, 2018 at 9:02 AM Barbara Pruijn  > wrote:
> Hi all,
> 
> Nice work on getting the 1.6.0 release out the door!  Next up is 1.7.0.  
> We’ve finished around 200 issues since the last release. 
> 
> Any one want to volunteer for release manager?  If you haven’t done this 
> before and would like to try, please review [1].
> 
> 
> Barbara
> 
> [1] 
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
>  
> 
>  
>   
> >  
> 
>  
>   
> >>

Re: Next release 1.7.0

[Nabarun Nag]

Hi Barbara,

I volunteer to be the release manager for Apache Geode 1.7.0.

Regards
Naba
[image: giphy.gif]

On Fri, May 18, 2018 at 9:02 AM Barbara Pruijn  wrote:

> Hi all,
>
> Nice work on getting the 1.6.0 release out the door!  Next up is 1.7.0.
> We’ve finished around 200 issues since the last release.
>
> Any one want to volunteer for release manager?  If you haven’t done this
> before and would like to try, please review [1].
>
>
> Barbara
>
> [1]
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
> <
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
> ><
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
> <
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
> >>

Re: Next release 1.7.0

[Anthony Baker]

I agree, I think we need to do a release.  I ran into GEODE-3563 setting up an 
SSL-enabled cluster and I’m anxious to get that fix out.

Here’s the full list of fixes:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012318420%20AND%20fixVersion%20%3D%2012343041%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC


Anthony


> On May 18, 2018, at 9:01 AM, Barbara Pruijn  wrote:
> 
> Hi all,
> 
> Nice work on getting the 1.6.0 release out the door!  Next up is 1.7.0.  
> We’ve finished around 200 issues since the last release. 
> 
> Any one want to volunteer for release manager?  If you haven’t done this 
> before and would like to try, please review [1].
> 
> 
> Barbara
> 
> [1] 
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
>  
>   
> >

Next release 1.7.0

[Barbara Pruijn]

Hi all,

Nice work on getting the 1.6.0 release out the door!  Next up is 1.7.0.  We’ve 
finished around 200 issues since the last release. 

Any one want to volunteer for release manager?  If you haven’t done this before 
and would like to try, please review [1].


Barbara

[1] 
https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
 
>

Re: Next release: 1.5.0

[Anthony Baker]

Thanks, John.  I did a round of updates for this release and expect we can 
continue do this in subsequent releases.

Bundled dependencies:
Commons Lang is at *3.7;* Geode is at 2.6
Log4j is at *2.10.0*; Geode is at 2.8.2
Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final
Spring Security is at *5.0.3.RELEASE*; Geode is at 4.2.4.RELEASE.
Spring Framework is at *5.0.3.RELEASE*; Geode is at 4.3.14.RELEASE

Non-bundled dependencies:
AssertJ is at *3.9.1;  *Geode is at 3.8.0
Mockito is at *2.15.0*; Geode is at 2.8.9
JSON Path is at *2.4.0*; Geode is at 2.2.0
Tomcat is at *8.5.28*; Geode is at 8.5.9.


I haven’t explored the Spring update to see how painful that will be.  I do 
like the dependency management plugin provided by Spring and would like to 
incorporate that into our build.  The log4j update to 2.10.0 had some conflicts 
with jetty IIRC so I backed off on that one for this release.

Anthony


> On Mar 6, 2018, at 9:31 AM, John Blum  wrote:
> 
> I also noticed that there are several outdated dependency versions yet...
> 
> AssertJ is at *3.9.1;  *Geode is at 3.8.0
> Commons Lang is at *3.7;* Geode is at 2.6
> JSON Path is at *2.4.0*; Geode is at 2.2.0
> Log4j is at *2.10.0*; Geode is at 2.8.2
> Mockito is at *2.15.0*; Geode is at 2.8.9
> Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final
> Spring Security is at *5.0.3.RELEASE*; Geode is at 4.2.4.RELEASE.
> Spring Framework is at *5.0.3.RELEASE*; Geode is at 4.3.14.RELEASE
> Tomcat is at *8.5.28*; Geode is at 8.5.9.
> 
> NOTE: the separate spring-tx.version is not needed as it does not differ
> from the core Spring Framework.
> NOTE: it would probably be easier to import the Spring Framework BOM file
> than individual Spring Framework deps.
> 
> These are just want I noticed at a quick glance when comparing to the *Spring
> Boot/Spring IO Platform* curated and managed set of dependencies.
> 
> -j
> 
> 
> 
> 
> On Tue, Mar 6, 2018 at 9:06 AM, Anthony Baker  > wrote:
> 
>> Looks like there are some things broken related to serialization filtering
>> as well on the release branch:
>> 
>> https://concourse.apachegeode-ci.info/teams/main/pipelines/ 
>> 
>> release-1.5.0/jobs/DistributedTest/builds/2 > .
>> apachegeode-ci.info/teams/main/pipelines/release-1.5.0/ 
>> 
>> jobs/DistributedTest/builds/2>
>> 
>> Anthony
>> 
>> 
>>> On Mar 6, 2018, at 8:57 AM, John Blum >> > wrote:
>>> 
>>> I don't think this should wait since it affects downstream artifacts
>>> (already)... Pivotal GemFire -> PCC.
>>> 
>>> As I stated, I am will have the changes prepared a few hours.  This is
>>> pretty low risk from Apache Geode's side but is imperative for Spring/PCC
>>> users.
>>> 
>>> On Tue, Mar 6, 2018 at 8:40 AM, Alexander Murmann >> >
>>> wrote:
>>> 
 John, how much of an issue would it be if the change was added one month
 from now?
 
 On Tue, Mar 6, 2018 at 8:36 AM, John Blum > wrote:
 
> I have 1 addition (planning to submit a PR for review) for the 1.5
 release
> that is imperative for *Spring Data for Apache Geode*, and
>> specifically,
> client-side Cluster Configuration Push [1].
> 
> Details to follow soon; will file a ticket in JIRA.
> 
> -j
> 
> 
> [1]
> https://docs.spring.io/spring-data/geode/docs/current/
> reference/html/#bootstrap-annotation-config-cluster
> 
> 
> On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker 
>> wrote:
> 
>> Could you make the pipeline public?
>> 
>> Anthony
>> 
>> 
>>> On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
>>> 
>>> 1.5.0 pipeline is up and running, please take a look at it and let
 the
>> list
>>> know if there are problems.
>>> 
>>> https://concourse.apachegeode-ci.info/teams/main/pipelines/
> release-1.5.0
>>> 
>>> On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
>> wrote:
>>> 
 LGTM
 
> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar  
 wrote:
> 
> Thanks Dave!
> 
> All, I have created a release branch (
> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> 
> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes 
> wrote:
> 
>> Status on the 3 doc issues:
>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
>> GEODE-4101:  redirect-output - Done
>> GEODE-3948: client timeout - Done

Re: Next release: 1.5.0

[John Blum]

I also noticed that there are several outdated dependency versions yet...

AssertJ is at *3.9.1;  *Geode is at 3.8.0
Commons Lang is at *3.7;* Geode is at 2.6
JSON Path is at *2.4.0*; Geode is at 2.2.0
Log4j is at *2.10.0*; Geode is at 2.8.2
Mockito is at *2.15.0*; Geode is at 2.8.9
Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final
Spring Security is at *5.0.3.RELEASE*; Geode is at 4.2.4.RELEASE.
Spring Framework is at *5.0.3.RELEASE*; Geode is at 4.3.14.RELEASE
Tomcat is at *8.5.28*; Geode is at 8.5.9.

NOTE: the separate spring-tx.version is not needed as it does not differ
from the core Spring Framework.
NOTE: it would probably be easier to import the Spring Framework BOM file
than individual Spring Framework deps.

These are just want I noticed at a quick glance when comparing to the *Spring
Boot/Spring IO Platform* curated and managed set of dependencies.

-j




On Tue, Mar 6, 2018 at 9:06 AM, Anthony Baker  wrote:

> Looks like there are some things broken related to serialization filtering
> as well on the release branch:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/
> release-1.5.0/jobs/DistributedTest/builds/2  apachegeode-ci.info/teams/main/pipelines/release-1.5.0/
> jobs/DistributedTest/builds/2>
>
> Anthony
>
>
> > On Mar 6, 2018, at 8:57 AM, John Blum  wrote:
> >
> > I don't think this should wait since it affects downstream artifacts
> > (already)... Pivotal GemFire -> PCC.
> >
> > As I stated, I am will have the changes prepared a few hours.  This is
> > pretty low risk from Apache Geode's side but is imperative for Spring/PCC
> > users.
> >
> > On Tue, Mar 6, 2018 at 8:40 AM, Alexander Murmann 
> > wrote:
> >
> >> John, how much of an issue would it be if the change was added one month
> >> from now?
> >>
> >> On Tue, Mar 6, 2018 at 8:36 AM, John Blum  wrote:
> >>
> >>> I have 1 addition (planning to submit a PR for review) for the 1.5
> >> release
> >>> that is imperative for *Spring Data for Apache Geode*, and
> specifically,
> >>> client-side Cluster Configuration Push [1].
> >>>
> >>> Details to follow soon; will file a ticket in JIRA.
> >>>
> >>> -j
> >>>
> >>>
> >>> [1]
> >>> https://docs.spring.io/spring-data/geode/docs/current/
> >>> reference/html/#bootstrap-annotation-config-cluster
> >>>
> >>>
> >>> On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker 
> wrote:
> >>>
>  Could you make the pipeline public?
> 
>  Anthony
> 
> 
> > On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> >
> > 1.5.0 pipeline is up and running, please take a look at it and let
> >> the
>  list
> > know if there are problems.
> >
> > https://concourse.apachegeode-ci.info/teams/main/pipelines/
> >>> release-1.5.0
> >
> > On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
>  wrote:
> >
> >> LGTM
> >>
> >>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar  >>>
> >> wrote:
> >>>
> >>> Thanks Dave!
> >>>
> >>> All, I have created a release branch (
> >>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> >>>
> >>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes 
> >>> wrote:
> >>>
>  Status on the 3 doc issues:
>  GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
>  GEODE-4101:  redirect-output - Done
>  GEODE-3948: client timeout - Done
> 
> 
>  On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar <
>  sbawas...@pivotal.io
> >>>
>  wrote:
> 
> > I will take up the release management task for 1.5.0
> >
> > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
> >> wrote:
> >
> >> Status on the 3 doc issues:
> >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it
> >>> covered
> >> GEODE-4101:  redirect-output  - Dave, in process, on track
> >> GEODE-3948: client timeout - Dave, in process. Probably on
> >> track -
> >> will
> >> keep you posted
> >>
> >> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker <
> >>> aba...@pivotal.io>
> > wrote:
> >>
> >>> Just checking in as we’re approaching the end of February.
> >> We’ve
> >> finished
> >>> around 200 issues and enhancements with 3 documentation updates
>  open
> > [1].
> >>> Is this a good time for another release?
> >>>
> >>> Any takers to do the release management tasks for 1.5.0?
> >>>
> >>> Anthony
> >>>
> >>> [1] https://issues.apache.org/jira/projects/GEODE/versions/
>  12342395
>  <
> >>> https://issues.apache.org/jira/projects/GEODE/versions/
> >> 12342395>
> >>>
> >>>
>  On Feb 7, 2018, 

Re: Next release: 1.5.0

[Anthony Baker]

Looks like there are some things broken related to serialization filtering as 
well on the release branch:

https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/2
 


Anthony


> On Mar 6, 2018, at 8:57 AM, John Blum  wrote:
> 
> I don't think this should wait since it affects downstream artifacts
> (already)... Pivotal GemFire -> PCC.
> 
> As I stated, I am will have the changes prepared a few hours.  This is
> pretty low risk from Apache Geode's side but is imperative for Spring/PCC
> users.
> 
> On Tue, Mar 6, 2018 at 8:40 AM, Alexander Murmann 
> wrote:
> 
>> John, how much of an issue would it be if the change was added one month
>> from now?
>> 
>> On Tue, Mar 6, 2018 at 8:36 AM, John Blum  wrote:
>> 
>>> I have 1 addition (planning to submit a PR for review) for the 1.5
>> release
>>> that is imperative for *Spring Data for Apache Geode*, and specifically,
>>> client-side Cluster Configuration Push [1].
>>> 
>>> Details to follow soon; will file a ticket in JIRA.
>>> 
>>> -j
>>> 
>>> 
>>> [1]
>>> https://docs.spring.io/spring-data/geode/docs/current/
>>> reference/html/#bootstrap-annotation-config-cluster
>>> 
>>> 
>>> On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker  wrote:
>>> 
 Could you make the pipeline public?
 
 Anthony
 
 
> On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> 
> 1.5.0 pipeline is up and running, please take a look at it and let
>> the
 list
> know if there are problems.
> 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/
>>> release-1.5.0
> 
> On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
 wrote:
> 
>> LGTM
>> 
>>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar >> 
>> wrote:
>>> 
>>> Thanks Dave!
>>> 
>>> All, I have created a release branch (
>>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
>>> 
>>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes 
>>> wrote:
>>> 
 Status on the 3 doc issues:
 GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
 GEODE-4101:  redirect-output - Done
 GEODE-3948: client timeout - Done
 
 
 On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar <
 sbawas...@pivotal.io
>>> 
 wrote:
 
> I will take up the release management task for 1.5.0
> 
> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
>> wrote:
> 
>> Status on the 3 doc issues:
>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it
>>> covered
>> GEODE-4101:  redirect-output  - Dave, in process, on track
>> GEODE-3948: client timeout - Dave, in process. Probably on
>> track -
>> will
>> keep you posted
>> 
>> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker <
>>> aba...@pivotal.io>
> wrote:
>> 
>>> Just checking in as we’re approaching the end of February.
>> We’ve
>> finished
>>> around 200 issues and enhancements with 3 documentation updates
 open
> [1].
>>> Is this a good time for another release?
>>> 
>>> Any takers to do the release management tasks for 1.5.0?
>>> 
>>> Anthony
>>> 
>>> [1] https://issues.apache.org/jira/projects/GEODE/versions/
 12342395
 <
>>> https://issues.apache.org/jira/projects/GEODE/versions/
>> 12342395>
>>> 
>>> 
 On Feb 7, 2018, at 1:56 PM, Anthony Baker 
 wrote:
 
 Hi all,
 
 Nice work on getting the 1.4.0 release out the door!  Next up
>> is
> 1.5.0.
>>> Any one want to volunteer for release manager?  If you haven’t
>>> done
> this
>>> before and would like to try, please review [1].
 
 I’ve been advocating for more frequent releases.  I’d love
>> see a
> March
>>> release—which means we would need to be ready to cut the
>> release
 branch
>> in
>>> early March.
 
 Thoughts?
 
 Anthony
 
 [1]
>> https://cwiki.apache.org/confluence/display/GEODE/
 Release+Steps?src=
>>> contextnavpagetreemode <
>> https://cwiki.apache.org/confluence/display/GEODE/
>>> Release+Steps?src=contextnavpagetreemode>
 
>>> 
>>> 
>> 
> 
 
>> 
>> 
 
 
>>> 
>>> 
>>> --
>>> -John
>>> john.blum10101 (skype)
>>> 
>> 
> 
> 
> 
> -- 
> -John
> john.blum10101 (skype)

Re: Next release: 1.5.0

[John Blum]

I don't think this should wait since it affects downstream artifacts
(already)... Pivotal GemFire -> PCC.

As I stated, I am will have the changes prepared a few hours.  This is
pretty low risk from Apache Geode's side but is imperative for Spring/PCC
users.

On Tue, Mar 6, 2018 at 8:40 AM, Alexander Murmann 
wrote:

> John, how much of an issue would it be if the change was added one month
> from now?
>
> On Tue, Mar 6, 2018 at 8:36 AM, John Blum  wrote:
>
> > I have 1 addition (planning to submit a PR for review) for the 1.5
> release
> > that is imperative for *Spring Data for Apache Geode*, and specifically,
> > client-side Cluster Configuration Push [1].
> >
> > Details to follow soon; will file a ticket in JIRA.
> >
> > -j
> >
> >
> > [1]
> > https://docs.spring.io/spring-data/geode/docs/current/
> > reference/html/#bootstrap-annotation-config-cluster
> >
> >
> > On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker  wrote:
> >
> > > Could you make the pipeline public?
> > >
> > > Anthony
> > >
> > >
> > > > On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> > > >
> > > > 1.5.0 pipeline is up and running, please take a look at it and let
> the
> > > list
> > > > know if there are problems.
> > > >
> > > > https://concourse.apachegeode-ci.info/teams/main/pipelines/
> > release-1.5.0
> > > >
> > > > On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
> > > wrote:
> > > >
> > > >> LGTM
> > > >>
> > > >>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar  >
> > > >> wrote:
> > > >>>
> > > >>> Thanks Dave!
> > > >>>
> > > >>> All, I have created a release branch (
> > > >>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> > > >>>
> > > >>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes 
> > wrote:
> > > >>>
> > >  Status on the 3 doc issues:
> > >  GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
> > >  GEODE-4101:  redirect-output - Done
> > >  GEODE-3948: client timeout - Done
> > > 
> > > 
> > >  On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar <
> > > sbawas...@pivotal.io
> > > >>>
> > >  wrote:
> > > 
> > > > I will take up the release management task for 1.5.0
> > > >
> > > > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
> > > >> wrote:
> > > >
> > > >> Status on the 3 doc issues:
> > > >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it
> > covered
> > > >> GEODE-4101:  redirect-output  - Dave, in process, on track
> > > >> GEODE-3948: client timeout - Dave, in process. Probably on
> track -
> > > >> will
> > > >> keep you posted
> > > >>
> > > >> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker <
> > aba...@pivotal.io>
> > > > wrote:
> > > >>
> > > >>> Just checking in as we’re approaching the end of February.
> We’ve
> > > >> finished
> > > >>> around 200 issues and enhancements with 3 documentation updates
> > > open
> > > > [1].
> > > >>> Is this a good time for another release?
> > > >>>
> > > >>> Any takers to do the release management tasks for 1.5.0?
> > > >>>
> > > >>> Anthony
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/projects/GEODE/versions/
> > > 12342395
> > >  <
> > > >>> https://issues.apache.org/jira/projects/GEODE/versions/
> 12342395>
> > > >>>
> > > >>>
> > >  On Feb 7, 2018, at 1:56 PM, Anthony Baker 
> > >  wrote:
> > > 
> > >  Hi all,
> > > 
> > >  Nice work on getting the 1.4.0 release out the door!  Next up
> is
> > > > 1.5.0.
> > > >>> Any one want to volunteer for release manager?  If you haven’t
> > done
> > > > this
> > > >>> before and would like to try, please review [1].
> > > 
> > >  I’ve been advocating for more frequent releases.  I’d love
> see a
> > > > March
> > > >>> release—which means we would need to be ready to cut the
> release
> > >  branch
> > > >> in
> > > >>> early March.
> > > 
> > >  Thoughts?
> > > 
> > >  Anthony
> > > 
> > >  [1]
> > > >> https://cwiki.apache.org/confluence/display/GEODE/
> > > Release+Steps?src=
> > > >>> contextnavpagetreemode <
> > > >> https://cwiki.apache.org/confluence/display/GEODE/
> > > >>> Release+Steps?src=contextnavpagetreemode>
> > > 
> > > >>>
> > > >>>
> > > >>
> > > >
> > > 
> > > >>
> > > >>
> > >
> > >
> >
> >
> > --
> > -John
> > john.blum10101 (skype)
> >
>



-- 
-John
john.blum10101 (skype)

Re: Next release: 1.5.0

[Alexander Murmann]

John, how much of an issue would it be if the change was added one month
from now?

On Tue, Mar 6, 2018 at 8:36 AM, John Blum  wrote:

> I have 1 addition (planning to submit a PR for review) for the 1.5 release
> that is imperative for *Spring Data for Apache Geode*, and specifically,
> client-side Cluster Configuration Push [1].
>
> Details to follow soon; will file a ticket in JIRA.
>
> -j
>
>
> [1]
> https://docs.spring.io/spring-data/geode/docs/current/
> reference/html/#bootstrap-annotation-config-cluster
>
>
> On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker  wrote:
>
> > Could you make the pipeline public?
> >
> > Anthony
> >
> >
> > > On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> > >
> > > 1.5.0 pipeline is up and running, please take a look at it and let the
> > list
> > > know if there are problems.
> > >
> > > https://concourse.apachegeode-ci.info/teams/main/pipelines/
> release-1.5.0
> > >
> > > On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
> > wrote:
> > >
> > >> LGTM
> > >>
> > >>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar 
> > >> wrote:
> > >>>
> > >>> Thanks Dave!
> > >>>
> > >>> All, I have created a release branch (
> > >>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> > >>>
> > >>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes 
> wrote:
> > >>>
> >  Status on the 3 doc issues:
> >  GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
> >  GEODE-4101:  redirect-output - Done
> >  GEODE-3948: client timeout - Done
> > 
> > 
> >  On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar <
> > sbawas...@pivotal.io
> > >>>
> >  wrote:
> > 
> > > I will take up the release management task for 1.5.0
> > >
> > > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
> > >> wrote:
> > >
> > >> Status on the 3 doc issues:
> > >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it
> covered
> > >> GEODE-4101:  redirect-output  - Dave, in process, on track
> > >> GEODE-3948: client timeout - Dave, in process. Probably on track -
> > >> will
> > >> keep you posted
> > >>
> > >> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker <
> aba...@pivotal.io>
> > > wrote:
> > >>
> > >>> Just checking in as we’re approaching the end of February.  We’ve
> > >> finished
> > >>> around 200 issues and enhancements with 3 documentation updates
> > open
> > > [1].
> > >>> Is this a good time for another release?
> > >>>
> > >>> Any takers to do the release management tasks for 1.5.0?
> > >>>
> > >>> Anthony
> > >>>
> > >>> [1] https://issues.apache.org/jira/projects/GEODE/versions/
> > 12342395
> >  <
> > >>> https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> > >>>
> > >>>
> >  On Feb 7, 2018, at 1:56 PM, Anthony Baker 
> >  wrote:
> > 
> >  Hi all,
> > 
> >  Nice work on getting the 1.4.0 release out the door!  Next up is
> > > 1.5.0.
> > >>> Any one want to volunteer for release manager?  If you haven’t
> done
> > > this
> > >>> before and would like to try, please review [1].
> > 
> >  I’ve been advocating for more frequent releases.  I’d love see a
> > > March
> > >>> release—which means we would need to be ready to cut the release
> >  branch
> > >> in
> > >>> early March.
> > 
> >  Thoughts?
> > 
> >  Anthony
> > 
> >  [1]
> > >> https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Steps?src=
> > >>> contextnavpagetreemode <
> > >> https://cwiki.apache.org/confluence/display/GEODE/
> > >>> Release+Steps?src=contextnavpagetreemode>
> > 
> > >>>
> > >>>
> > >>
> > >
> > 
> > >>
> > >>
> >
> >
>
>
> --
> -John
> john.blum10101 (skype)
>

Re: Next release: 1.5.0

[John Blum]

I have 1 addition (planning to submit a PR for review) for the 1.5 release
that is imperative for *Spring Data for Apache Geode*, and specifically,
client-side Cluster Configuration Push [1].

Details to follow soon; will file a ticket in JIRA.

-j


[1]
https://docs.spring.io/spring-data/geode/docs/current/reference/html/#bootstrap-annotation-config-cluster


On Mon, Mar 5, 2018 at 1:09 PM, Anthony Baker  wrote:

> Could you make the pipeline public?
>
> Anthony
>
>
> > On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> >
> > 1.5.0 pipeline is up and running, please take a look at it and let the
> list
> > know if there are problems.
> >
> > https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0
> >
> > On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker 
> wrote:
> >
> >> LGTM
> >>
> >>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar 
> >> wrote:
> >>>
> >>> Thanks Dave!
> >>>
> >>> All, I have created a release branch (
> >>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> >>>
> >>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes  wrote:
> >>>
>  Status on the 3 doc issues:
>  GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
>  GEODE-4101:  redirect-output - Done
>  GEODE-3948: client timeout - Done
> 
> 
>  On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar <
> sbawas...@pivotal.io
> >>>
>  wrote:
> 
> > I will take up the release management task for 1.5.0
> >
> > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
> >> wrote:
> >
> >> Status on the 3 doc issues:
> >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
> >> GEODE-4101:  redirect-output  - Dave, in process, on track
> >> GEODE-3948: client timeout - Dave, in process. Probably on track -
> >> will
> >> keep you posted
> >>
> >> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
> > wrote:
> >>
> >>> Just checking in as we’re approaching the end of February.  We’ve
> >> finished
> >>> around 200 issues and enhancements with 3 documentation updates
> open
> > [1].
> >>> Is this a good time for another release?
> >>>
> >>> Any takers to do the release management tasks for 1.5.0?
> >>>
> >>> Anthony
> >>>
> >>> [1] https://issues.apache.org/jira/projects/GEODE/versions/
> 12342395
>  <
> >>> https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> >>>
> >>>
>  On Feb 7, 2018, at 1:56 PM, Anthony Baker 
>  wrote:
> 
>  Hi all,
> 
>  Nice work on getting the 1.4.0 release out the door!  Next up is
> > 1.5.0.
> >>> Any one want to volunteer for release manager?  If you haven’t done
> > this
> >>> before and would like to try, please review [1].
> 
>  I’ve been advocating for more frequent releases.  I’d love see a
> > March
> >>> release—which means we would need to be ready to cut the release
>  branch
> >> in
> >>> early March.
> 
>  Thoughts?
> 
>  Anthony
> 
>  [1]
> >> https://cwiki.apache.org/confluence/display/GEODE/
> Release+Steps?src=
> >>> contextnavpagetreemode <
> >> https://cwiki.apache.org/confluence/display/GEODE/
> >>> Release+Steps?src=contextnavpagetreemode>
> 
> >>>
> >>>
> >>
> >
> 
> >>
> >>
>
>


-- 
-John
john.blum10101 (skype)

Re: Next release: 1.5.0

[Anthony Baker]

Could you make the pipeline public?

Anthony


> On Mar 5, 2018, at 12:46 PM, Sean Goller  wrote:
> 
> 1.5.0 pipeline is up and running, please take a look at it and let the list
> know if there are problems.
> 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0
> 
> On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker  wrote:
> 
>> LGTM
>> 
>>> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar 
>> wrote:
>>> 
>>> Thanks Dave!
>>> 
>>> All, I have created a release branch (
>>> https://github.com/apache/geode/tree/release/1.5.0) Please review.
>>> 
>>> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes  wrote:
>>> 
 Status on the 3 doc issues:
 GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
 GEODE-4101:  redirect-output - Done
 GEODE-3948: client timeout - Done
 
 
 On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar >> 
 wrote:
 
> I will take up the release management task for 1.5.0
> 
> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
>> wrote:
> 
>> Status on the 3 doc issues:
>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
>> GEODE-4101:  redirect-output  - Dave, in process, on track
>> GEODE-3948: client timeout - Dave, in process. Probably on track -
>> will
>> keep you posted
>> 
>> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
> wrote:
>> 
>>> Just checking in as we’re approaching the end of February.  We’ve
>> finished
>>> around 200 issues and enhancements with 3 documentation updates open
> [1].
>>> Is this a good time for another release?
>>> 
>>> Any takers to do the release management tasks for 1.5.0?
>>> 
>>> Anthony
>>> 
>>> [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395
 <
>>> https://issues.apache.org/jira/projects/GEODE/versions/12342395>
>>> 
>>> 
 On Feb 7, 2018, at 1:56 PM, Anthony Baker 
 wrote:
 
 Hi all,
 
 Nice work on getting the 1.4.0 release out the door!  Next up is
> 1.5.0.
>>> Any one want to volunteer for release manager?  If you haven’t done
> this
>>> before and would like to try, please review [1].
 
 I’ve been advocating for more frequent releases.  I’d love see a
> March
>>> release—which means we would need to be ready to cut the release
 branch
>> in
>>> early March.
 
 Thoughts?
 
 Anthony
 
 [1]
>> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
>>> contextnavpagetreemode <
>> https://cwiki.apache.org/confluence/display/GEODE/
>>> Release+Steps?src=contextnavpagetreemode>
 
>>> 
>>> 
>> 
> 
 
>> 
>> 

Re: Next release: 1.5.0

[Sean Goller]

1.5.0 pipeline is up and running, please take a look at it and let the list
know if there are problems.

https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0

On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker  wrote:

> LGTM
>
> > On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar 
> wrote:
> >
> > Thanks Dave!
> >
> > All, I have created a release branch (
> > https://github.com/apache/geode/tree/release/1.5.0) Please review.
> >
> > On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes  wrote:
> >
> >> Status on the 3 doc issues:
> >> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
> >> GEODE-4101:  redirect-output - Done
> >> GEODE-3948: client timeout - Done
> >>
> >>
> >> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar  >
> >> wrote:
> >>
> >>> I will take up the release management task for 1.5.0
> >>>
> >>> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes 
> wrote:
> >>>
>  Status on the 3 doc issues:
>  GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
>  GEODE-4101:  redirect-output  - Dave, in process, on track
>  GEODE-3948: client timeout - Dave, in process. Probably on track -
> will
>  keep you posted
> 
>  On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
> >>> wrote:
> 
> > Just checking in as we’re approaching the end of February.  We’ve
>  finished
> > around 200 issues and enhancements with 3 documentation updates open
> >>> [1].
> > Is this a good time for another release?
> >
> > Any takers to do the release management tasks for 1.5.0?
> >
> > Anthony
> >
> > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395
> >> <
> > https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> >
> >
> >> On Feb 7, 2018, at 1:56 PM, Anthony Baker 
> >> wrote:
> >>
> >> Hi all,
> >>
> >> Nice work on getting the 1.4.0 release out the door!  Next up is
> >>> 1.5.0.
> > Any one want to volunteer for release manager?  If you haven’t done
> >>> this
> > before and would like to try, please review [1].
> >>
> >> I’ve been advocating for more frequent releases.  I’d love see a
> >>> March
> > release—which means we would need to be ready to cut the release
> >> branch
>  in
> > early March.
> >>
> >> Thoughts?
> >>
> >> Anthony
> >>
> >> [1]
>  https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> > contextnavpagetreemode <
>  https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Steps?src=contextnavpagetreemode>
> >>
> >
> >
> 
> >>>
> >>
>
>

Re: Next release: 1.5.0

[Anthony Baker]

LGTM

> On Mar 2, 2018, at 4:05 PM, Swapnil Bawaskar  wrote:
> 
> Thanks Dave!
> 
> All, I have created a release branch (
> https://github.com/apache/geode/tree/release/1.5.0) Please review.
> 
> On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes  wrote:
> 
>> Status on the 3 doc issues:
>> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
>> GEODE-4101:  redirect-output - Done
>> GEODE-3948: client timeout - Done
>> 
>> 
>> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar 
>> wrote:
>> 
>>> I will take up the release management task for 1.5.0
>>> 
>>> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes  wrote:
>>> 
 Status on the 3 doc issues:
 GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
 GEODE-4101:  redirect-output  - Dave, in process, on track
 GEODE-3948: client timeout - Dave, in process. Probably on track - will
 keep you posted
 
 On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
>>> wrote:
 
> Just checking in as we’re approaching the end of February.  We’ve
 finished
> around 200 issues and enhancements with 3 documentation updates open
>>> [1].
> Is this a good time for another release?
> 
> Any takers to do the release management tasks for 1.5.0?
> 
> Anthony
> 
> [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395
>> <
> https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> 
> 
>> On Feb 7, 2018, at 1:56 PM, Anthony Baker 
>> wrote:
>> 
>> Hi all,
>> 
>> Nice work on getting the 1.4.0 release out the door!  Next up is
>>> 1.5.0.
> Any one want to volunteer for release manager?  If you haven’t done
>>> this
> before and would like to try, please review [1].
>> 
>> I’ve been advocating for more frequent releases.  I’d love see a
>>> March
> release—which means we would need to be ready to cut the release
>> branch
 in
> early March.
>> 
>> Thoughts?
>> 
>> Anthony
>> 
>> [1]
 https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> contextnavpagetreemode <
 https://cwiki.apache.org/confluence/display/GEODE/
> Release+Steps?src=contextnavpagetreemode>
>> 
> 
> 
 
>>> 
>> 

Re: Next release: 1.5.0

[Swapnil Bawaskar]

Thanks Dave!

All, I have created a release branch (
https://github.com/apache/geode/tree/release/1.5.0) Please review.

On Fri, Mar 2, 2018 at 9:56 AM Dave Barnes  wrote:

> Status on the 3 doc issues:
> GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
> GEODE-4101:  redirect-output - Done
> GEODE-3948: client timeout - Done
>
>
> On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar 
> wrote:
>
> > I will take up the release management task for 1.5.0
> >
> > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes  wrote:
> >
> > > Status on the 3 doc issues:
> > > GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
> > > GEODE-4101:  redirect-output  - Dave, in process, on track
> > > GEODE-3948: client timeout - Dave, in process. Probably on track - will
> > > keep you posted
> > >
> > > On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
> > wrote:
> > >
> > > > Just checking in as we’re approaching the end of February.  We’ve
> > > finished
> > > > around 200 issues and enhancements with 3 documentation updates open
> > [1].
> > > > Is this a good time for another release?
> > > >
> > > > Any takers to do the release management tasks for 1.5.0?
> > > >
> > > > Anthony
> > > >
> > > > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395
> <
> > > > https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> > > >
> > > >
> > > > > On Feb 7, 2018, at 1:56 PM, Anthony Baker 
> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Nice work on getting the 1.4.0 release out the door!  Next up is
> > 1.5.0.
> > > > Any one want to volunteer for release manager?  If you haven’t done
> > this
> > > > before and would like to try, please review [1].
> > > > >
> > > > > I’ve been advocating for more frequent releases.  I’d love see a
> > March
> > > > release—which means we would need to be ready to cut the release
> branch
> > > in
> > > > early March.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Anthony
> > > > >
> > > > > [1]
> > > https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> > > > contextnavpagetreemode <
> > > https://cwiki.apache.org/confluence/display/GEODE/
> > > > Release+Steps?src=contextnavpagetreemode>
> > > > >
> > > >
> > > >
> > >
> >
>

Re: Next release: 1.5.0

[Dave Barnes]

Status on the 3 doc issues:
GEODE-4737 / GEODE-3915: JSON args in gfsh - Done
GEODE-4101:  redirect-output - Done
GEODE-3948: client timeout - Done


On Thu, Mar 1, 2018 at 11:22 AM, Swapnil Bawaskar 
wrote:

> I will take up the release management task for 1.5.0
>
> On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes  wrote:
>
> > Status on the 3 doc issues:
> > GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
> > GEODE-4101:  redirect-output  - Dave, in process, on track
> > GEODE-3948: client timeout - Dave, in process. Probably on track - will
> > keep you posted
> >
> > On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker 
> wrote:
> >
> > > Just checking in as we’re approaching the end of February.  We’ve
> > finished
> > > around 200 issues and enhancements with 3 documentation updates open
> [1].
> > > Is this a good time for another release?
> > >
> > > Any takers to do the release management tasks for 1.5.0?
> > >
> > > Anthony
> > >
> > > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 <
> > > https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> > >
> > >
> > > > On Feb 7, 2018, at 1:56 PM, Anthony Baker  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Nice work on getting the 1.4.0 release out the door!  Next up is
> 1.5.0.
> > > Any one want to volunteer for release manager?  If you haven’t done
> this
> > > before and would like to try, please review [1].
> > > >
> > > > I’ve been advocating for more frequent releases.  I’d love see a
> March
> > > release—which means we would need to be ready to cut the release branch
> > in
> > > early March.
> > > >
> > > > Thoughts?
> > > >
> > > > Anthony
> > > >
> > > > [1]
> > https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> > > contextnavpagetreemode <
> > https://cwiki.apache.org/confluence/display/GEODE/
> > > Release+Steps?src=contextnavpagetreemode>
> > > >
> > >
> > >
> >
>

Re: Next release: 1.5.0

[Swapnil Bawaskar]

I will take up the release management task for 1.5.0

On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes  wrote:

> Status on the 3 doc issues:
> GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
> GEODE-4101:  redirect-output  - Dave, in process, on track
> GEODE-3948: client timeout - Dave, in process. Probably on track - will
> keep you posted
>
> On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker  wrote:
>
> > Just checking in as we’re approaching the end of February.  We’ve
> finished
> > around 200 issues and enhancements with 3 documentation updates open [1].
> > Is this a good time for another release?
> >
> > Any takers to do the release management tasks for 1.5.0?
> >
> > Anthony
> >
> > [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 <
> > https://issues.apache.org/jira/projects/GEODE/versions/12342395>
> >
> >
> > > On Feb 7, 2018, at 1:56 PM, Anthony Baker  wrote:
> > >
> > > Hi all,
> > >
> > > Nice work on getting the 1.4.0 release out the door!  Next up is 1.5.0.
> > Any one want to volunteer for release manager?  If you haven’t done this
> > before and would like to try, please review [1].
> > >
> > > I’ve been advocating for more frequent releases.  I’d love see a March
> > release—which means we would need to be ready to cut the release branch
> in
> > early March.
> > >
> > > Thoughts?
> > >
> > > Anthony
> > >
> > > [1]
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> > contextnavpagetreemode <
> https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Steps?src=contextnavpagetreemode>
> > >
> >
> >
>

Re: Next release: 1.5.0

[Dave Barnes]

Status on the 3 doc issues:
GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered
GEODE-4101:  redirect-output  - Dave, in process, on track
GEODE-3948: client timeout - Dave, in process. Probably on track - will
keep you posted

On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker  wrote:

> Just checking in as we’re approaching the end of February.  We’ve finished
> around 200 issues and enhancements with 3 documentation updates open [1].
> Is this a good time for another release?
>
> Any takers to do the release management tasks for 1.5.0?
>
> Anthony
>
> [1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 <
> https://issues.apache.org/jira/projects/GEODE/versions/12342395>
>
>
> > On Feb 7, 2018, at 1:56 PM, Anthony Baker  wrote:
> >
> > Hi all,
> >
> > Nice work on getting the 1.4.0 release out the door!  Next up is 1.5.0.
> Any one want to volunteer for release manager?  If you haven’t done this
> before and would like to try, please review [1].
> >
> > I’ve been advocating for more frequent releases.  I’d love see a March
> release—which means we would need to be ready to cut the release branch in
> early March.
> >
> > Thoughts?
> >
> > Anthony
> >
> > [1] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=
> contextnavpagetreemode  Release+Steps?src=contextnavpagetreemode>
> >
>
>

Re: Next release: 1.5.0

[Anthony Baker]

Just checking in as we’re approaching the end of February.  We’ve finished 
around 200 issues and enhancements with 3 documentation updates open [1].  Is 
this a good time for another release?

Any takers to do the release management tasks for 1.5.0?

Anthony

[1] https://issues.apache.org/jira/projects/GEODE/versions/12342395 



> On Feb 7, 2018, at 1:56 PM, Anthony Baker  wrote:
> 
> Hi all,
> 
> Nice work on getting the 1.4.0 release out the door!  Next up is 1.5.0.  Any 
> one want to volunteer for release manager?  If you haven’t done this before 
> and would like to try, please review [1].
> 
> I’ve been advocating for more frequent releases.  I’d love see a March 
> release—which means we would need to be ready to cut the release branch in 
> early March.
> 
> Thoughts?
> 
> Anthony
> 
> [1] 
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
>  
> 
> 

Next release: 1.5.0

[Anthony Baker]

Hi all,

Nice work on getting the 1.4.0 release out the door!  Next up is 1.5.0.  Any 
one want to volunteer for release manager?  If you haven’t done this before and 
would like to try, please review [1].

I’ve been advocating for more frequent releases.  I’d love see a March 
release—which means we would need to be ready to cut the release branch in 
early March.

Thoughts?

Anthony

[1] 
https://cwiki.apache.org/confluence/display/GEODE/Release+Steps?src=contextnavpagetreemode
 

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 <amurm...@pivotal.io>
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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
> > > > <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > > > 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 <aba...@pivotal.io
> >
> > > > 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 <aba...@pivotal.io> 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 <amurm...@pivotal.io>

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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
<https://issues.apache.org/jira/secure/RapidBoard.jspa?
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 <aba...@pivotal.io>

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 <aba...@pivotal.io> 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 <amurm...@pivotal.io>
> 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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
> >>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> >>>> 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 <aba...@pivotal.io>
> >>>> 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 <aging...@pivotal.io>
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 <aba...@pivotal.io> 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 <amurm...@pivotal.io>
> > 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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
> > >>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > >>>> 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 <aba...@pivotal.io>
> > >>>> 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 <aba...@pivotal.io> 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 <amurm...@pivotal.io>
> 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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
> >>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> >>>> 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 <aba...@pivotal.io>
> >>>> 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 <amurm...@pivotal.io> 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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?
>>>> 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 <aba...@pivotal.io>
>>>> 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 <jhu...@pivotal.io> 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 <dsm...@pivotal.io> 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
> > > <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > > 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 <aba...@pivotal.io>
> > > 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 <dsm...@pivotal.io> 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
> > <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> > 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 <aba...@pivotal.io>
> > 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 <sbawas...@pivotal.io>
wrote:

> Since all the issues tagged for 1.4.0 release
> <https://issues.apache.org/jira/secure/RapidBoard.jspa?
> 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 <aba...@pivotal.io>
> 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
<https://issues.apache.org/jira/secure/RapidBoard.jspa?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 <aba...@pivotal.io> 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 <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 <aba...@pivotal.io> 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 <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 <aba...@pivotal.io> 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 <aba...@pivotal.io> wrote:

> Bump.  Any volunteers?  If not, I’ll do this.
>
> Anthony
>
>
> > On Nov 22, 2017, at 1:48 PM, Anthony Baker <aba...@pivotal.io> 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 <aba...@pivotal.io> 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 <aba...@pivotal.io> 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
>
>

Next release: 1.4.0

[Anthony Baker]

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: Question regarding the next release

[Anthony Baker]

The community is working hard to ensure that backwards compatibility is 
preserved.

There are currently 2 open issues remaining to be fixed:
https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012318420%20AND%20fixVersion%20%3D%2012339257%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
 


Once those are complete we’ll create another release candidate.

Anthony

> On Jun 29, 2017, at 3:06 AM, Roi Apelker  wrote:
> 
> Hi,
> 
> Is there an expected date for release of 1.2?
> 
> Are there any backward compatibility issues in this version? If so, are they 
> documented separately from the other issues?
> 
> Thanks,
> 
> Roi
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer 
> 

Question regarding the next release

[Roi Apelker]

Hi,

Is there an expected date for release of 1.2?

Are there any backward compatibility issues in this version? If so, are they 
documented separately from the other issues?

Thanks,

Roi
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

Re: The next release (v1.1.0)

[Michael Stolz]

Yay!
+1

--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771

On Fri, Jan 27, 2017 at 6:40 AM, Anthony Baker <aba...@pivotal.io> wrote:

> Looks like all the JIRA’s for v1.1.0  have been wrapped up [1].  I say
> let’s cut a release branch and move ahead.
>
> Anthony
>
> [1] https://issues.apache.org/jira/browse/GEODE/fixforversion/12338352/?
> selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>
> > On Jan 24, 2017, at 1:14 PM, Mark Bretl <mbr...@apache.org> wrote:
> >
> > Do we think we can get these done and get a release before the next board
> > meeting (2/15)? I think it would be an excellent point on our report.
> >
> > Best Regards,
> >
> > --Mark
> >
> > On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
> > hitesh...@yahoo.com.invalid> wrote:
> >
> >> Update: Three more ticket for first release candidate..
> >>
> >> GEODE-2300 Document default names for start locator/server
> >> GEODE-2353 Verify no clear-text passwords in documentation
> >> GEODE-2282 Provide ability to sort field while creating pdxType for jSON
> >> document(Need to document system property)
> >>
> >> Thanks.HItesh
> >>
> >>
> >>
> >>  From: Hitesh Khamesra <hitesh...@yahoo.com>
> >> To: "dev@geode.apache.org" <dev@geode.apache.org>
> >> Sent: Monday, January 16, 2017 12:35 PM
> >> Subject: Re: The next release (v1.1.0)
> >>
> >> Update: We are waiting on following tickets for first release candidate.
> >>
> >> 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse
> User
> >> Exception
> >> 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
> >> InternalGemFireError
> >> 3.  GEODE-2031 Host documentation for releases
> >> 4.  GEODE-1965 Create backward-compatibility unit test framework
> >>
> >> Thanks.HItesh
> >>
> >>  From: Anthony Baker <aba...@pivotal.io>
> >> To: dev@geode.apache.org
> >> Sent: Monday, January 9, 2017 9:49 AM
> >> Subject: Re: The next release (v1.1.0)
> >>
> >> Updates:
> >>
> >> 1) I did a first round of changes on GEODE-2142, should be enough for
> >> v1.1.0.
> >> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> >> 3) Are there other open issues that should be included in the release?
> >> 4) Last call for a release manager…  :-)
> >>
> >> Thanks,
> >> Anthony
> >>
> >>
> >>> On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >>>
> >>> Our last release was on October 25.  I think we’re past due for another
> >> one!  We’ve had lots of great contributions since 1.0.0-incubating and
> now
> >> that we’re are a top-level project we can drop the “-incubating”
> qualifier.
> >>>
> >>> I reviewed our open JIRA issues and would like to include the following
> >> in the release:
> >>>
> >>> GEODE-2142 - JSON license incompatibility
> >>>We can update the NOTICE files and leave the JSON dependency alone
> >> (as long as we do another release before April 30).
> >>>
> >>> GEODE-1965 - backwards compatibility tests
> >>>I’d like to make sure we haven’t broken anything since our last
> >> release.
> >>>
> >>> GEODE-2031 - versioned documentation
> >>>Seems relatively straightforward?
> >>>
> >>> The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> >> a following release IMO.  Thoughts?
> >>>
> >>> Regarding the release manager, I can do the dirty work if no one else
> >> wants to volunteer :-)
> >>>
> >>> Anthony
> >>>
> >>> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
> >> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
> >> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> >> 20DESC%2C%20created%20ASC
> >>>
> >>>> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >>>>
> >>>> Now that graduation is done (!!), we need to organize our next
> >> release.  I propose we focus on completing the transition to TLP and
> >> cleaning up “incubating" references.  The sequence would look something
> >> like this:
> >>>>
> >>>> 1) Transition the git repo, mailing lists, etc.
> >>>> 2) Update incubating references in source, docs, website, wiki, …
> >>>> 3) Do a release.
> >>>>
> >>>> Thoughts?
> >>>>
> >>>> We need a release manager.  Any volunteers?
> >>>>
> >>>> Also, we need to rename the JIRA version from 1.1.0-incubating to
> >> 1.1.0.  Can someone with JIRA karma help?
> >>>>
> >>>> Anthony
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

Re: The next release (v1.1.0)

[Anthony Baker]

Looks like all the JIRA’s for v1.1.0  have been wrapped up [1].  I say let’s 
cut a release branch and move ahead.

Anthony

[1] 
https://issues.apache.org/jira/browse/GEODE/fixforversion/12338352/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel

> On Jan 24, 2017, at 1:14 PM, Mark Bretl <mbr...@apache.org> wrote:
> 
> Do we think we can get these done and get a release before the next board
> meeting (2/15)? I think it would be an excellent point on our report.
> 
> Best Regards,
> 
> --Mark
> 
> On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
> hitesh...@yahoo.com.invalid> wrote:
> 
>> Update: Three more ticket for first release candidate..
>> 
>> GEODE-2300 Document default names for start locator/server
>> GEODE-2353 Verify no clear-text passwords in documentation
>> GEODE-2282 Provide ability to sort field while creating pdxType for jSON
>> document(Need to document system property)
>> 
>> Thanks.HItesh
>> 
>> 
>> 
>>  From: Hitesh Khamesra <hitesh...@yahoo.com>
>> To: "dev@geode.apache.org" <dev@geode.apache.org>
>> Sent: Monday, January 16, 2017 12:35 PM
>> Subject: Re: The next release (v1.1.0)
>> 
>> Update: We are waiting on following tickets for first release candidate.
>> 
>> 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User
>> Exception
>> 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
>> InternalGemFireError
>> 3.  GEODE-2031 Host documentation for releases
>> 4.  GEODE-1965 Create backward-compatibility unit test framework
>> 
>> Thanks.HItesh
>> 
>>  From: Anthony Baker <aba...@pivotal.io>
>> To: dev@geode.apache.org
>> Sent: Monday, January 9, 2017 9:49 AM
>> Subject: Re: The next release (v1.1.0)
>> 
>> Updates:
>> 
>> 1) I did a first round of changes on GEODE-2142, should be enough for
>> v1.1.0.
>> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
>> 3) Are there other open issues that should be included in the release?
>> 4) Last call for a release manager…  :-)
>> 
>> Thanks,
>> Anthony
>> 
>> 
>>> On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
>>> 
>>> Our last release was on October 25.  I think we’re past due for another
>> one!  We’ve had lots of great contributions since 1.0.0-incubating and now
>> that we’re are a top-level project we can drop the “-incubating” qualifier.
>>> 
>>> I reviewed our open JIRA issues and would like to include the following
>> in the release:
>>> 
>>> GEODE-2142 - JSON license incompatibility
>>>We can update the NOTICE files and leave the JSON dependency alone
>> (as long as we do another release before April 30).
>>> 
>>> GEODE-1965 - backwards compatibility tests
>>>I’d like to make sure we haven’t broken anything since our last
>> release.
>>> 
>>> GEODE-2031 - versioned documentation
>>>Seems relatively straightforward?
>>> 
>>> The remaining issues that are tagged with v1.1.0 [1] could be pushed to
>> a following release IMO.  Thoughts?
>>> 
>>> Regarding the release manager, I can do the dirty work if no one else
>> wants to volunteer :-)
>>> 
>>> Anthony
>>> 
>>> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
>> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
>> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
>> 20DESC%2C%20created%20ASC
>>> 
>>>> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
>>>> 
>>>> Now that graduation is done (!!), we need to organize our next
>> release.  I propose we focus on completing the transition to TLP and
>> cleaning up “incubating" references.  The sequence would look something
>> like this:
>>>> 
>>>> 1) Transition the git repo, mailing lists, etc.
>>>> 2) Update incubating references in source, docs, website, wiki, …
>>>> 3) Do a release.
>>>> 
>>>> Thoughts?
>>>> 
>>>> We need a release manager.  Any volunteers?
>>>> 
>>>> Also, we need to rename the JIRA version from 1.1.0-incubating to
>> 1.1.0.  Can someone with JIRA karma help?
>>>> 
>>>> Anthony
>>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 

Re: The next release (v1.1.0)

[Dave Barnes]

Sorry, I was reading too quickly. The third one should be do-able, as well.

On Tue, Jan 24, 2017 at 1:23 PM, Dave Barnes <dbar...@pivotal.io> wrote:

> The first two are doc tasks - should be no problem to get them done by
> 2/15.
>
> On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl <mbr...@apache.org> wrote:
>
>> Do we think we can get these done and get a release before the next board
>> meeting (2/15)? I think it would be an excellent point on our report.
>>
>> Best Regards,
>>
>> --Mark
>>
>> On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
>> hitesh...@yahoo.com.invalid> wrote:
>>
>> > Update: Three more ticket for first release candidate..
>> >
>> > GEODE-2300 Document default names for start locator/server
>> > GEODE-2353 Verify no clear-text passwords in documentation
>> > GEODE-2282 Provide ability to sort field while creating pdxType for jSON
>> > document(Need to document system property)
>> >
>> > Thanks.HItesh
>> >
>> >
>> >
>> >   From: Hitesh Khamesra <hitesh...@yahoo.com>
>> >  To: "dev@geode.apache.org" <dev@geode.apache.org>
>> >  Sent: Monday, January 16, 2017 12:35 PM
>> >  Subject: Re: The next release (v1.1.0)
>> >
>> > Update: We are waiting on following tickets for first release candidate.
>> >
>> > 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse
>> User
>> > Exception
>> > 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
>> > InternalGemFireError
>> > 3.  GEODE-2031 Host documentation for releases
>> > 4.  GEODE-1965 Create backward-compatibility unit test framework
>> >
>> > Thanks.HItesh
>> >
>> >   From: Anthony Baker <aba...@pivotal.io>
>> >  To: dev@geode.apache.org
>> >  Sent: Monday, January 9, 2017 9:49 AM
>> >  Subject: Re: The next release (v1.1.0)
>> >
>> > Updates:
>> >
>> > 1) I did a first round of changes on GEODE-2142, should be enough for
>> > v1.1.0.
>> > 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
>> > 3) Are there other open issues that should be included in the release?
>> > 4) Last call for a release manager…  :-)
>> >
>> > Thanks,
>> > Anthony
>> >
>> >
>> > > On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
>> > >
>> > > Our last release was on October 25.  I think we’re past due for
>> another
>> > one!  We’ve had lots of great contributions since 1.0.0-incubating and
>> now
>> > that we’re are a top-level project we can drop the “-incubating”
>> qualifier.
>> > >
>> > > I reviewed our open JIRA issues and would like to include the
>> following
>> > in the release:
>> > >
>> > > GEODE-2142 - JSON license incompatibility
>> > > We can update the NOTICE files and leave the JSON dependency alone
>> > (as long as we do another release before April 30).
>> > >
>> > > GEODE-1965 - backwards compatibility tests
>> > > I’d like to make sure we haven’t broken anything since our last
>> > release.
>> > >
>> > > GEODE-2031 - versioned documentation
>> > > Seems relatively straightforward?
>> > >
>> > > The remaining issues that are tagged with v1.1.0 [1] could be pushed
>> to
>> > a following release IMO.  Thoughts?
>> > >
>> > > Regarding the release manager, I can do the dirty work if no one else
>> > wants to volunteer :-)
>> > >
>> > > Anthony
>> > >
>> > > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
>> > EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
>> > 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
>> > 20DESC%2C%20created%20ASC
>> > >
>> > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io>
>> wrote:
>> > >>
>> > >> Now that graduation is done (!!), we need to organize our next
>> > release.  I propose we focus on completing the transition to TLP and
>> > cleaning up “incubating" references.  The sequence would look something
>> > like this:
>> > >>
>> > >> 1) Transition the git repo, mailing lists, etc.
>> > >> 2) Update incubating references in source, docs, website, wiki, …
>> > >> 3) Do a release.
>> > >>
>> > >> Thoughts?
>> > >>
>> > >> We need a release manager.  Any volunteers?
>> > >>
>> > >> Also, we need to rename the JIRA version from 1.1.0-incubating to
>> > 1.1.0.  Can someone with JIRA karma help?
>> > >>
>> > >> Anthony
>> > >>
>> > >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>

Re: The next release (v1.1.0)

[Dave Barnes]

The first two are doc tasks - should be no problem to get them done by 2/15.

On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl <mbr...@apache.org> wrote:

> Do we think we can get these done and get a release before the next board
> meeting (2/15)? I think it would be an excellent point on our report.
>
> Best Regards,
>
> --Mark
>
> On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
> hitesh...@yahoo.com.invalid> wrote:
>
> > Update: Three more ticket for first release candidate..
> >
> > GEODE-2300 Document default names for start locator/server
> > GEODE-2353 Verify no clear-text passwords in documentation
> > GEODE-2282 Provide ability to sort field while creating pdxType for jSON
> > document(Need to document system property)
> >
> > Thanks.HItesh
> >
> >
> >
> >   From: Hitesh Khamesra <hitesh...@yahoo.com>
> >  To: "dev@geode.apache.org" <dev@geode.apache.org>
> >  Sent: Monday, January 16, 2017 12:35 PM
> >  Subject: Re: The next release (v1.1.0)
> >
> > Update: We are waiting on following tickets for first release candidate.
> >
> > 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse
> User
> > Exception
> > 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
> > InternalGemFireError
> > 3.  GEODE-2031 Host documentation for releases
> > 4.  GEODE-1965 Create backward-compatibility unit test framework
> >
> > Thanks.HItesh
> >
> >   From: Anthony Baker <aba...@pivotal.io>
> >  To: dev@geode.apache.org
> >  Sent: Monday, January 9, 2017 9:49 AM
> >  Subject: Re: The next release (v1.1.0)
> >
> > Updates:
> >
> > 1) I did a first round of changes on GEODE-2142, should be enough for
> > v1.1.0.
> > 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> > 3) Are there other open issues that should be included in the release?
> > 4) Last call for a release manager…  :-)
> >
> > Thanks,
> > Anthony
> >
> >
> > > On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> > >
> > > Our last release was on October 25.  I think we’re past due for another
> > one!  We’ve had lots of great contributions since 1.0.0-incubating and
> now
> > that we’re are a top-level project we can drop the “-incubating”
> qualifier.
> > >
> > > I reviewed our open JIRA issues and would like to include the following
> > in the release:
> > >
> > > GEODE-2142 - JSON license incompatibility
> > > We can update the NOTICE files and leave the JSON dependency alone
> > (as long as we do another release before April 30).
> > >
> > > GEODE-1965 - backwards compatibility tests
> > > I’d like to make sure we haven’t broken anything since our last
> > release.
> > >
> > > GEODE-2031 - versioned documentation
> > > Seems relatively straightforward?
> > >
> > > The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> > a following release IMO.  Thoughts?
> > >
> > > Regarding the release manager, I can do the dirty work if no one else
> > wants to volunteer :-)
> > >
> > > Anthony
> > >
> > > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
> > EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
> > 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> > 20DESC%2C%20created%20ASC
> > >
> > >> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
> > >>
> > >> Now that graduation is done (!!), we need to organize our next
> > release.  I propose we focus on completing the transition to TLP and
> > cleaning up “incubating" references.  The sequence would look something
> > like this:
> > >>
> > >> 1) Transition the git repo, mailing lists, etc.
> > >> 2) Update incubating references in source, docs, website, wiki, …
> > >> 3) Do a release.
> > >>
> > >> Thoughts?
> > >>
> > >> We need a release manager.  Any volunteers?
> > >>
> > >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> > 1.1.0.  Can someone with JIRA karma help?
> > >>
> > >> Anthony
> > >>
> > >
> >
> >
> >
> >
> >
> >
>

Re: The next release (v1.1.0)

[Mark Bretl]

Do we think we can get these done and get a release before the next board
meeting (2/15)? I think it would be an excellent point on our report.

Best Regards,

--Mark

On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
hitesh...@yahoo.com.invalid> wrote:

> Update: Three more ticket for first release candidate..
>
> GEODE-2300 Document default names for start locator/server
> GEODE-2353 Verify no clear-text passwords in documentation
> GEODE-2282 Provide ability to sort field while creating pdxType for jSON
> document(Need to document system property)
>
> Thanks.HItesh
>
>
>
>   From: Hitesh Khamesra <hitesh...@yahoo.com>
>  To: "dev@geode.apache.org" <dev@geode.apache.org>
>  Sent: Monday, January 16, 2017 12:35 PM
>  Subject: Re: The next release (v1.1.0)
>
> Update: We are waiting on following tickets for first release candidate.
>
> 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User
> Exception
> 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
> InternalGemFireError
> 3.  GEODE-2031 Host documentation for releases
> 4.  GEODE-1965 Create backward-compatibility unit test framework
>
> Thanks.HItesh
>
>   From: Anthony Baker <aba...@pivotal.io>
>  To: dev@geode.apache.org
>  Sent: Monday, January 9, 2017 9:49 AM
>  Subject: Re: The next release (v1.1.0)
>
> Updates:
>
> 1) I did a first round of changes on GEODE-2142, should be enough for
> v1.1.0.
> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> 3) Are there other open issues that should be included in the release?
> 4) Last call for a release manager…  :-)
>
> Thanks,
> Anthony
>
>
> > On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >
> > Our last release was on October 25.  I think we’re past due for another
> one!  We’ve had lots of great contributions since 1.0.0-incubating and now
> that we’re are a top-level project we can drop the “-incubating” qualifier.
> >
> > I reviewed our open JIRA issues and would like to include the following
> in the release:
> >
> > GEODE-2142 - JSON license incompatibility
> > We can update the NOTICE files and leave the JSON dependency alone
> (as long as we do another release before April 30).
> >
> > GEODE-1965 - backwards compatibility tests
> > I’d like to make sure we haven’t broken anything since our last
> release.
> >
> > GEODE-2031 - versioned documentation
> > Seems relatively straightforward?
> >
> > The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> a following release IMO.  Thoughts?
> >
> > Regarding the release manager, I can do the dirty work if no one else
> wants to volunteer :-)
> >
> > Anthony
> >
> > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> 20DESC%2C%20created%20ASC
> >
> >> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >>
> >> Now that graduation is done (!!), we need to organize our next
> release.  I propose we focus on completing the transition to TLP and
> cleaning up “incubating" references.  The sequence would look something
> like this:
> >>
> >> 1) Transition the git repo, mailing lists, etc.
> >> 2) Update incubating references in source, docs, website, wiki, …
> >> 3) Do a release.
> >>
> >> Thoughts?
> >>
> >> We need a release manager.  Any volunteers?
> >>
> >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >>
> >> Anthony
> >>
> >
>
>
>
>
>
>

Re: The next release (v1.1.0)

[Hitesh Khamesra]

Update: Three more ticket for first release candidate..

GEODE-2300 Document default names for start locator/server
GEODE-2353 Verify no clear-text passwords in documentation
GEODE-2282 Provide ability to sort field while creating pdxType for jSON 
document(Need to document system property)

Thanks.HItesh



  From: Hitesh Khamesra <hitesh...@yahoo.com>
 To: "dev@geode.apache.org" <dev@geode.apache.org> 
 Sent: Monday, January 16, 2017 12:35 PM
 Subject: Re: The next release (v1.1.0)
   
Update: We are waiting on following tickets for first release candidate.

1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User 
Exception
2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to 
InternalGemFireError
3.  GEODE-2031 Host documentation for releases 
4.  GEODE-1965 Create backward-compatibility unit test framework 

Thanks.HItesh

  From: Anthony Baker <aba...@pivotal.io>
 To: dev@geode.apache.org 
 Sent: Monday, January 9, 2017 9:49 AM
 Subject: Re: The next release (v1.1.0)
  
Updates:

1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0.
2) Any volunteers to look at GEODE-2031 or GEODE-1965?
3) Are there other open issues that should be included in the release?
4) Last call for a release manager…  :-)

Thanks,
Anthony


> On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> 
> Our last release was on October 25.  I think we’re past due for another one!  
> We’ve had lots of great contributions since 1.0.0-incubating and now that 
> we’re are a top-level project we can drop the “-incubating” qualifier.
> 
> I reviewed our open JIRA issues and would like to include the following in 
> the release:
> 
> GEODE-2142 - JSON license incompatibility
>     We can update the NOTICE files and leave the JSON dependency alone (as 
> long as we do another release before April 30).
> 
> GEODE-1965 - backwards compatibility tests
>     I’d like to make sure we haven’t broken anything since our last release.
> 
> GEODE-2031 - versioned documentation
>     Seems relatively straightforward?
> 
> The remaining issues that are tagged with v1.1.0 [1] could be pushed to a 
> following release IMO.  Thoughts?
> 
> Regarding the release manager, I can do the dirty work if no one else wants 
> to volunteer :-)
> 
> Anthony
> 
> [1] 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
>> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
>> 
>> Now that graduation is done (!!), we need to organize our next release.  I 
>> propose we focus on completing the transition to TLP and cleaning up 
>> “incubating" references.  The sequence would look something like this:
>> 
>> 1) Transition the git repo, mailing lists, etc.
>> 2) Update incubating references in source, docs, website, wiki, …
>> 3) Do a release.
>> 
>> Thoughts?
>> 
>> We need a release manager.  Any volunteers?
>> 
>> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  
>> Can someone with JIRA karma help?
>> 
>> Anthony
>> 
> 


   

   

Re: The next release (v1.1.0)

[Hitesh Khamesra]

Update: We are waiting on following tickets for first release candidate.

1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User 
Exception
2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to 
InternalGemFireError
3.  GEODE-2031 Host documentation for releases 
4.  GEODE-1965 Create backward-compatibility unit test framework 

Thanks.HItesh

  From: Anthony Baker <aba...@pivotal.io>
 To: dev@geode.apache.org 
 Sent: Monday, January 9, 2017 9:49 AM
 Subject: Re: The next release (v1.1.0)
   
Updates:

1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0.
2) Any volunteers to look at GEODE-2031 or GEODE-1965?
3) Are there other open issues that should be included in the release?
4) Last call for a release manager…  :-)

Thanks,
Anthony


> On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> 
> Our last release was on October 25.  I think we’re past due for another one!  
> We’ve had lots of great contributions since 1.0.0-incubating and now that 
> we’re are a top-level project we can drop the “-incubating” qualifier.
> 
> I reviewed our open JIRA issues and would like to include the following in 
> the release:
> 
> GEODE-2142 - JSON license incompatibility
>     We can update the NOTICE files and leave the JSON dependency alone (as 
> long as we do another release before April 30).
> 
> GEODE-1965 - backwards compatibility tests
>     I’d like to make sure we haven’t broken anything since our last release.
> 
> GEODE-2031 - versioned documentation
>     Seems relatively straightforward?
> 
> The remaining issues that are tagged with v1.1.0 [1] could be pushed to a 
> following release IMO.  Thoughts?
> 
> Regarding the release manager, I can do the dirty work if no one else wants 
> to volunteer :-)
> 
> Anthony
> 
> [1] 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
>> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
>> 
>> Now that graduation is done (!!), we need to organize our next release.  I 
>> propose we focus on completing the transition to TLP and cleaning up 
>> “incubating" references.  The sequence would look something like this:
>> 
>> 1) Transition the git repo, mailing lists, etc.
>> 2) Update incubating references in source, docs, website, wiki, …
>> 3) Do a release.
>> 
>> Thoughts?
>> 
>> We need a release manager.  Any volunteers?
>> 
>> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  
>> Can someone with JIRA karma help?
>> 
>> Anthony
>> 
> 


   

Re: The next release (v1.1.0)

[Joey McAllister]

Re: 2) I'll take a look at GEODE-2031, versioning the documentation.

On Mon, Jan 9, 2017 at 9:50 AM Anthony Baker <aba...@pivotal.io> wrote:

> Updates:
>
> 1) I did a first round of changes on GEODE-2142, should be enough for
> v1.1.0.
> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> 3) Are there other open issues that should be included in the release?
> 4) Last call for a release manager…  :-)
>
> Thanks,
> Anthony
>
>
> > On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >
> > Our last release was on October 25.  I think we’re past due for another
> one!  We’ve had lots of great contributions since 1.0.0-incubating and now
> that we’re are a top-level project we can drop the “-incubating” qualifier.
> >
> > I reviewed our open JIRA issues and would like to include the following
> in the release:
> >
> > GEODE-2142 - JSON license incompatibility
> >   We can update the NOTICE files and leave the JSON dependency alone
> (as long as we do another release before April 30).
> >
> > GEODE-1965 - backwards compatibility tests
> >   I’d like to make sure we haven’t broken anything since our last
> release.
> >
> > GEODE-2031 - versioned documentation
> >   Seems relatively straightforward?
> >
> > The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> a following release IMO.  Thoughts?
> >
> > Regarding the release manager, I can do the dirty work if no one else
> wants to volunteer :-)
> >
> > Anthony
> >
> > [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> >> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
> >>
> >> Now that graduation is done (!!), we need to organize our next
> release.  I propose we focus on completing the transition to TLP and
> cleaning up “incubating" references.  The sequence would look something
> like this:
> >>
> >> 1) Transition the git repo, mailing lists, etc.
> >> 2) Update incubating references in source, docs, website, wiki, …
> >> 3) Do a release.
> >>
> >> Thoughts?
> >>
> >> We need a release manager.  Any volunteers?
> >>
> >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >>
> >> Anthony
> >>
> >
>
>

Re: The next release (v1.1.0)

[Anthony Baker]

Updates:

1) I did a first round of changes on GEODE-2142, should be enough for v1.1.0.
2) Any volunteers to look at GEODE-2031 or GEODE-1965?
3) Are there other open issues that should be included in the release?
4) Last call for a release manager…  :-)

Thanks,
Anthony


> On Jan 6, 2017, at 10:13 AM, Anthony Baker <aba...@pivotal.io> wrote:
> 
> Our last release was on October 25.  I think we’re past due for another one!  
> We’ve had lots of great contributions since 1.0.0-incubating and now that 
> we’re are a top-level project we can drop the “-incubating” qualifier.
> 
> I reviewed our open JIRA issues and would like to include the following in 
> the release:
> 
> GEODE-2142 - JSON license incompatibility
>   We can update the NOTICE files and leave the JSON dependency alone (as 
> long as we do another release before April 30).
> 
> GEODE-1965 - backwards compatibility tests
>   I’d like to make sure we haven’t broken anything since our last release.
> 
> GEODE-2031 - versioned documentation
>   Seems relatively straightforward?
> 
> The remaining issues that are tagged with v1.1.0 [1] could be pushed to a 
> following release IMO.  Thoughts?
> 
> Regarding the release manager, I can do the dirty work if no one else wants 
> to volunteer :-)
> 
> Anthony
> 
> [1] 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
>> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
>> 
>> Now that graduation is done (!!), we need to organize our next release.  I 
>> propose we focus on completing the transition to TLP and cleaning up 
>> “incubating" references.  The sequence would look something like this:
>> 
>> 1) Transition the git repo, mailing lists, etc.
>> 2) Update incubating references in source, docs, website, wiki, …
>> 3) Do a release.
>> 
>> Thoughts?
>> 
>> We need a release manager.  Any volunteers?
>> 
>> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  
>> Can someone with JIRA karma help?
>> 
>> Anthony
>> 
> 

Re: The next release (v1.1.0)

[Anthony Baker]

Our last release was on October 25.  I think we’re past due for another one!  
We’ve had lots of great contributions since 1.0.0-incubating and now that we’re 
are a top-level project we can drop the “-incubating” qualifier.

I reviewed our open JIRA issues and would like to include the following in the 
release:

GEODE-2142 - JSON license incompatibility
We can update the NOTICE files and leave the JSON dependency alone (as 
long as we do another release before April 30).

GEODE-1965 - backwards compatibility tests
I’d like to make sure we haven’t broken anything since our last release.

GEODE-2031 - versioned documentation
Seems relatively straightforward?

The remaining issues that are tagged with v1.1.0 [1] could be pushed to a 
following release IMO.  Thoughts?

Regarding the release manager, I can do the dirty work if no one else wants to 
volunteer :-)

Anthony

[1] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

> On Nov 21, 2016, at 9:26 AM, Anthony Baker <aba...@pivotal.io> wrote:
> 
> Now that graduation is done (!!), we need to organize our next release.  I 
> propose we focus on completing the transition to TLP and cleaning up 
> “incubating" references.  The sequence would look something like this:
> 
> 1) Transition the git repo, mailing lists, etc.
> 2) Update incubating references in source, docs, website, wiki, …
> 3) Do a release.
> 
> Thoughts?
> 
> We need a release manager.  Any volunteers?
> 
> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  Can 
> someone with JIRA karma help?
> 
> Anthony
> 

Re: The next release (v1.1.0)

[Dan Smith]

+1 to getting this stuff cleaned up. I'd really like to see us get into a
more regular release cadence.

I renamed 1.1.0-incubating to 1.1.0 in JIRA.

Dor - I don't think any of the active committers are planning on leaving.
We're working on this project because we want it to thrive, and graduation
is one more thing that will help it grow!

-Dan

On Wed, Nov 23, 2016 at 1:03 AM, Dor Ben Dov <dor.ben-...@amdocs.com> wrote:

> Anthony,
>
> Are you (all pivotal developers / architects) who are here in the
> community will now leave once this being managed by
> Itself or are you continuing to contribute?
> Regards,
> Dor
>
> -Original Message-
> From: Anthony Baker [mailto:aba...@pivotal.io]
> Sent: יום ג 22 נובמבר 2016 16:44
> To: geode <d...@geode.incubator.apache.org>
> Subject: Re: The next release (v1.1.0)
>
> Transitioning from an incubating project to a top-level project means we
> keep doing exactly what we’ve been doing—except that now the project is
> responsible for managing itself.  We will be transitioning a few resources
> such as mailing lists and git repos to reflect that we are no longer an
> incubator subproject.
>
> See http://incubator.apache.org/guides/graduation.html.
>
> Anthony
>
> > On Nov 21, 2016, at 11:57 AM, Dor Ben Dov <dor.ben-...@amdocs.com>
> wrote:
> >
> > Anthony,
> >
> > What are the actual implications of this transition to the tlp ?
> >
> > Regards,
> > Dor
> >
> > -Original Message-
> > From: Anthony Baker [mailto:aba...@pivotal.io]
> > Sent: יום ב 21 נובמבר 2016 19:26
> > To: dev@geode.apache.org
> > Subject: The next release (v1.1.0)
> >
> > Now that graduation is done (!!), we need to organize our next release.
> I propose we focus on completing the transition to TLP and cleaning up
> “incubating" references.  The sequence would look something like this:
> >
> > 1) Transition the git repo, mailing lists, etc.
> > 2) Update incubating references in source, docs, website, wiki, …
> > 3) Do a release.
> >
> > Thoughts?
> >
> > We need a release manager.  Any volunteers?
> >
> > Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >
> > Anthony
> >
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement, you may
> > review at http://www.amdocs.com/email_disclaimer.asp
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>

RE: The next release (v1.1.0)

[Dor Ben Dov]

Anthony, 

What are the actual implications of this transition to the tlp ? 

Regards,
Dor

-Original Message-
From: Anthony Baker [mailto:aba...@pivotal.io] 
Sent: יום ב 21 נובמבר 2016 19:26
To: dev@geode.apache.org
Subject: The next release (v1.1.0)

Now that graduation is done (!!), we need to organize our next release.  I 
propose we focus on completing the transition to TLP and cleaning up 
“incubating" references.  The sequence would look something like this:

1) Transition the git repo, mailing lists, etc.
2) Update incubating references in source, docs, website, wiki, …
3) Do a release.

Thoughts?

We need a release manager.  Any volunteers?

Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  Can 
someone with JIRA karma help?

Anthony


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp

The next release (v1.1.0)

[Anthony Baker]

Now that graduation is done (!!), we need to organize our next release.  I 
propose we focus on completing the transition to TLP and cleaning up 
“incubating" references.  The sequence would look something like this:

1) Transition the git repo, mailing lists, etc.
2) Update incubating references in source, docs, website, wiki, …
3) Do a release.

Thoughts?

We need a release manager.  Any volunteers?

Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  Can 
someone with JIRA karma help?

Anthony