Re: Proposal to bring GEODE-8016 to support branches

2020-05-11 Thread Owen Nichols
Thanks!  Change has been backported to 1.13 and 1.12.  Downstream projects can 
now use the new version selector syntax consistently across 1.12, 1.13, and 
1.14.  To recap, that means if you are a downstream project and you want the 
latest “nightly build” (formerly -SNAPSHOT) of Geode 1.12, 1.13, or 1.14 please 
use the maven repo url:

https://maven.apachegeode-ci.info/snapshots 


And change your geode- dependency version to a non-snapshot notation 
such as:

Gradle:
1.+ //latest 1.y.x
1.14.+//latest 1.14.x
1.13.+//latest 1.13.x
1.12.+//latest 1.12.x

Maven:
[1,2)  //latest 1.y.x
[1.14,1.15)//latest 1.14.x
[1.13,1.14)//latest 1.13.x
[1.12,1.13)//latest 1.12.x

> On May 11, 2020, at 10:49 AM, Dave Barnes  wrote:
> 
> Looks good, Owen. Go ahead and add this to 1.13.
> 
> On Mon, May 11, 2020 at 9:49 AM Robert Houghton 
> wrote:
> 
>> Yes please! +1
>> 
>> On Mon, May 11, 2020 at 2:46 AM Darrel Schneider 
>> wrote:
>> 
>>> +1
>>> 
>>> On Sun, May 10, 2020 at 10:05 PM Dick Cavender 
>>> wrote:
>>> 
 +1
 
 On Sat, May 9, 2020 at 6:42 PM Owen Nichols 
>> wrote:
 
> Last week develop was successfully migrated from publishing -SNAPSHOT
>>> to
> publishing -build.nnn, as discussed on the dev list.
> 
> I propose that we bring the same change to support/1.13 and
>>> support/1.12
> for consistency.  This will allow downstream projects to change over
>>> the
> new model “everywhere" rather than having to maintain support for
>> both
 ways
> and constantly try to remember which branches do it which way.
> 
> The specific changes to be cherry-picked from develop are a4c8b <
> 
 
>>> 
>> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048
> 
> and 39c52 <
> 
 
>>> 
>> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782
> .
> I have prepared PR #5089 
>>> for
> support/1.13 and PR #5090 >> 
 for
> support/1.12 due to the version number differences on each branch.
 
>>> 
>> 



Re: Proposal to bring GEODE-8016 to support branches

2020-05-11 Thread Dave Barnes
Looks good, Owen. Go ahead and add this to 1.13.

On Mon, May 11, 2020 at 9:49 AM Robert Houghton 
wrote:

> Yes please! +1
>
> On Mon, May 11, 2020 at 2:46 AM Darrel Schneider 
> wrote:
>
> > +1
> >
> > On Sun, May 10, 2020 at 10:05 PM Dick Cavender 
> > wrote:
> >
> > > +1
> > >
> > > On Sat, May 9, 2020 at 6:42 PM Owen Nichols 
> wrote:
> > >
> > > > Last week develop was successfully migrated from publishing -SNAPSHOT
> > to
> > > > publishing -build.nnn, as discussed on the dev list.
> > > >
> > > > I propose that we bring the same change to support/1.13 and
> > support/1.12
> > > > for consistency.  This will allow downstream projects to change over
> > the
> > > > new model “everywhere" rather than having to maintain support for
> both
> > > ways
> > > > and constantly try to remember which branches do it which way.
> > > >
> > > > The specific changes to be cherry-picked from develop are a4c8b <
> > > >
> > >
> >
> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048
> > > >
> > > > and 39c52 <
> > > >
> > >
> >
> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782
> > > >.
> > > > I have prepared PR #5089 
> > for
> > > > support/1.13 and PR #5090  >
> > > for
> > > > support/1.12 due to the version number differences on each branch.
> > >
> >
>


Re: Proposal to bring GEODE-8016 to support branches

2020-05-11 Thread Robert Houghton
Yes please! +1

On Mon, May 11, 2020 at 2:46 AM Darrel Schneider 
wrote:

> +1
>
> On Sun, May 10, 2020 at 10:05 PM Dick Cavender 
> wrote:
>
> > +1
> >
> > On Sat, May 9, 2020 at 6:42 PM Owen Nichols  wrote:
> >
> > > Last week develop was successfully migrated from publishing -SNAPSHOT
> to
> > > publishing -build.nnn, as discussed on the dev list.
> > >
> > > I propose that we bring the same change to support/1.13 and
> support/1.12
> > > for consistency.  This will allow downstream projects to change over
> the
> > > new model “everywhere" rather than having to maintain support for both
> > ways
> > > and constantly try to remember which branches do it which way.
> > >
> > > The specific changes to be cherry-picked from develop are a4c8b <
> > >
> >
> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048
> > >
> > > and 39c52 <
> > >
> >
> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782
> > >.
> > > I have prepared PR #5089 
> for
> > > support/1.13 and PR #5090 
> > for
> > > support/1.12 due to the version number differences on each branch.
> >
>


Re: Proposal to bring GEODE-8016 to support branches

2020-05-11 Thread Darrel Schneider
+1

On Sun, May 10, 2020 at 10:05 PM Dick Cavender  wrote:

> +1
>
> On Sat, May 9, 2020 at 6:42 PM Owen Nichols  wrote:
>
> > Last week develop was successfully migrated from publishing -SNAPSHOT to
> > publishing -build.nnn, as discussed on the dev list.
> >
> > I propose that we bring the same change to support/1.13 and support/1.12
> > for consistency.  This will allow downstream projects to change over the
> > new model “everywhere" rather than having to maintain support for both
> ways
> > and constantly try to remember which branches do it which way.
> >
> > The specific changes to be cherry-picked from develop are a4c8b <
> >
> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048
> >
> > and 39c52 <
> >
> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782
> >.
> > I have prepared PR #5089  for
> > support/1.13 and PR #5090 
> for
> > support/1.12 due to the version number differences on each branch.
>


Re: Proposal to bring GEODE-8016 to support branches

2020-05-10 Thread Dick Cavender
+1

On Sat, May 9, 2020 at 6:42 PM Owen Nichols  wrote:

> Last week develop was successfully migrated from publishing -SNAPSHOT to
> publishing -build.nnn, as discussed on the dev list.
>
> I propose that we bring the same change to support/1.13 and support/1.12
> for consistency.  This will allow downstream projects to change over the
> new model “everywhere" rather than having to maintain support for both ways
> and constantly try to remember which branches do it which way.
>
> The specific changes to be cherry-picked from develop are a4c8b <
> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048>
> and 39c52 <
> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782>.
> I have prepared PR #5089  for
> support/1.13 and PR #5090  for
> support/1.12 due to the version number differences on each branch.


Proposal to bring GEODE-8016 to support branches

2020-05-09 Thread Owen Nichols
Last week develop was successfully migrated from publishing -SNAPSHOT to 
publishing -build.nnn, as discussed on the dev list.

I propose that we bring the same change to support/1.13 and support/1.12 for 
consistency.  This will allow downstream projects to change over the new model 
“everywhere" rather than having to maintain support for both ways and 
constantly try to remember which branches do it which way.

The specific changes to be cherry-picked from develop are a4c8b 

 and 39c52 
.
  I have prepared PR #5089  for 
support/1.13 and PR #5090  for 
support/1.12 due to the version number differences on each branch.