Re: [PROPOSAL] Postpone Geode 1.14

2020-07-30 Thread Xiaojian Zhou 
+1

On 7/29/20, 1:35 PM, "Mark Bretl"  wrote:

+1

Should we need to drop a line to user@geode or is communicating on this
list enough once decided?

--Mark

On Wed, Jul 29, 2020 at 7:05 AM Joris Melchior  wrote:

> +1
>
> On 2020-07-28, 7:34 PM, "Alexander Murmann"  wrote:
>
> Hi all,
>
> As mentioned on the previous discuss thread, I propose to hold off
> cutting
> 1.14 until we have shipped 1.13.
>
> Once we have shipped 1.13, we should discuss when we want to cut the
> 1.14
> release. The actual ship date for Geode 1.13 is important information
> for
> that conversation. Thus we cannot have that conversation before then.
>
>

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Mark Bretl 
+1

--Mark

On Thu, Jul 30, 2020 at 1:30 PM Robert Houghton 
wrote:

> Highwater isn't used by benchmarks?
>
> On Jul 30, 2020 12:02, Dave Barnes  wrote:
> +1
>
> On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols  wrote:
>
> > Hi Donal, I can confirm that develop/highwater hasn't been updated in a
> > year and is no longer in use by any pipelines (all pipelines use the last
> > release tag as the benchmark baseline now).
> >
> > On 7/30/20, 5:48 AM, "Donal Evans"  wrote:
> >
> > I may be mistaken, but I think the develop/highwater tag was used by
> > the geode-benchmarks project. Can we get confirmation that it's no longer
> > in use?
> >
> > +1 conditional on that
> >
> > Get Outlook for Android<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Crhoughton%40vmware.com%7C399c0ee0d7824ffc4e5008d834bb2a3e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317325761204283sdata=xmzDLn4YsP4KyZl9vWEbY2pOzWHJDKef7dMtgtEHy3E%3Dreserved=0
> > >
> >
> > 
> > From: Ju@N 
> > Sent: Thursday, July 30, 2020 3:10:44 AM
> > To: dev@geode.apache.org 
> > Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags
> in
> > geode repo
> >
> > +1
> >
> > On Thu 30 Jul 2020 at 08:21, Owen Nichols 
> wrote:
> >
> > > Tags in the rel/ namespace should be created by the Geode release
> > manager
> > > as part of an official Geode release only, yet we seem to have some
> > extra
> > > ones somehow.
> > > Further, I don't see any value in keeping RC tags forever long
> after
> > the
> > > release is final.
> > >
> > > Please vote +1 in favor of trimming the current list of 110 tags
> > down to
> > > 20 to make it nice and easy for newcomers (as well as the rest of
> > us) to
> > > find and checkout a specific version of Geode; otherwise vote -1.
> > If the
> > > majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive
> > and
> > > delete the 90 unnecessary tags as detailed below.
> > >
> > > I propose to KEEP only the following tags, corresponding to
> official
> > Geode
> > > releases:
> > >
> > > rel/v1.12.0
> > > rel/v1.11.0
> > > rel/v1.10.0
> > > rel/v1.9.2
> > > rel/v1.9.1
> > > rel/v1.9.0
> > > rel/v1.8.0
> > > rel/v1.7.0
> > > rel/v1.6.0
> > > rel/v1.5.0
> > > rel/v1.4.0
> > > rel/v1.3.0
> > > rel/v1.2.1
> > > rel/v1.2.0
> > > rel/v1.1.1
> > > rel/v1.1.0
> > > rel/v1.0.0-incubating
> > > rel/v1.0.0-incubating.M3
> > > rel/v1.0.0-incubating.M2
> > > rel/v1.0.0-incubating.M1
> > >
> > > I propose a one-time cleanup to DELETE all other tags,
> specifically:
> > >
> > > develop/highwater
> > > modules-pre-merge
> > > rel/v1.0.0-incubating.M1.RC1
> > > rel/v1.0.0-incubating.M1.RC2
> > > rel/v1.0.0-incubating.M2.RC1
> > > rel/v1.0.0-incubating.M2.RC2
> > > rel/v1.0.0-incubating.M3.RC1
> > > rel/v1.0.0-incubating.M3.RC2
> > > rel/v1.0.0-incubating.M3.RC3
> > > rel/v1.0.0-incubating.M3.RC4
> > > rel/v1.0.0-incubating.M3.RC5
> > > rel/v1.0.0-incubating.M3.RC6
> > > rel/v1.0.0-incubating.M3.RC7
> > > rel/v1.0.0-incubating.RC1
> > > rel/v1.0.0-incubating.RC2
> > > rel/v1.1.0.RC1
> > > rel/v1.1.0.RC2
> > > rel/v1.1.0manualrev-2017-02-16
> > > rel/v1.1.0manualrev-2017-10-19
> > > rel/v1.1.1.RC1
> > > rel/v1.1.1.RC2
> > > rel/v1.10.0.1
> > > rel/v1.10.0.1.RC1
> > > rel/v1.10.0.2
> > > rel/v1.10.0.RC1
> > > rel/v1.10.0.RC2
> > > rel/v1.11.0.1
> > > rel/v1.11.0.2
> > > rel/v1.11.0.23755
> > > rel/v1.11.0.23755_2
> > > rel/v1.11.0.23755_3
> > > rel/v1.11.0.3
> > > rel/v1.11.0.4
> > > rel/v1.11.0.5
> > > rel/v1.11.0.6
> > > rel/v1.11.0.7
> > > rel/v1.11.0.7565
> > > rel/v1.11.0.8
> > > rel/v1.11.0.RC1
> > > rel/v1.11.0.RC2
> > > rel/v1.11.0.RC3
> > > rel/v1.11.0.RC4
> > > rel/v1.12.0.1
> > > rel/v1.12.0.1234
> > > rel/v1.12.0.2
> > > rel/v1.12.0.23755
> > > rel/v1.12.0.3
> > > rel/v1.12.0.4
> > > rel/v1.12.0.5
> > > rel/v1.12.0.6
> > > rel/v1.12.0.RC1
> > > rel/v1.12.0.RC2
> > > rel/v1.12.0.RC3
> > > rel/v1.12.0.RC4
> > > rel/v1.14.0.23755
> > > rel/v1.2.0.RC1
> > > rel/v1.2.0.RC2
> > > rel/v1.2.1.RC1
> > > rel/v1.2.1.RC2
> > > rel/v1.2.1.RC3
> > > rel/v1.2.1.RC4
> > > rel/v1.2.1manualrev-2017-10-19
> > > rel/v1.3.0.RC1
> > > rel/v1.3.0.RC2
> > > rel/v1.3.0.RC3
> > > rel/v1.3.0.RC4
> > > rel/v1.4.0.RC1
> > > rel/v1.4.0.RC2
> > > rel/v1.5.0.RC1
> > > rel/v1.5.0.RC2
> > > rel/v1.6.0.RC1
> > > rel/v1.7.0.RC1
> > > rel/v1.7.0.RC2
> > > rel/v1.8.0.RC1
> > > rel/v1.8.0.RC2
> > > rel/v1.9.0.1
> > > rel/v1.9.0.1.RC1
> > > rel/v1.9.0.2
> > > rel/v1.9.0.RC1

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Robert Houghton 
Highwater isn't used by benchmarks?

On Jul 30, 2020 12:02, Dave Barnes  wrote:
+1

On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols  wrote:

> Hi Donal, I can confirm that develop/highwater hasn't been updated in a
> year and is no longer in use by any pipelines (all pipelines use the last
> release tag as the benchmark baseline now).
>
> On 7/30/20, 5:48 AM, "Donal Evans"  wrote:
>
> I may be mistaken, but I think the develop/highwater tag was used by
> the geode-benchmarks project. Can we get confirmation that it's no longer
> in use?
>
> +1 conditional on that
>
> Get Outlook for Android<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Crhoughton%40vmware.com%7C399c0ee0d7824ffc4e5008d834bb2a3e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317325761204283sdata=xmzDLn4YsP4KyZl9vWEbY2pOzWHJDKef7dMtgtEHy3E%3Dreserved=0
> >
>
> 
> From: Ju@N 
> Sent: Thursday, July 30, 2020 3:10:44 AM
> To: dev@geode.apache.org 
> Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in
> geode repo
>
> +1
>
> On Thu 30 Jul 2020 at 08:21, Owen Nichols  wrote:
>
> > Tags in the rel/ namespace should be created by the Geode release
> manager
> > as part of an official Geode release only, yet we seem to have some
> extra
> > ones somehow.
> > Further, I don't see any value in keeping RC tags forever long after
> the
> > release is final.
> >
> > Please vote +1 in favor of trimming the current list of 110 tags
> down to
> > 20 to make it nice and easy for newcomers (as well as the rest of
> us) to
> > find and checkout a specific version of Geode; otherwise vote -1.
> If the
> > majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive
> and
> > delete the 90 unnecessary tags as detailed below.
> >
> > I propose to KEEP only the following tags, corresponding to official
> Geode
> > releases:
> >
> > rel/v1.12.0
> > rel/v1.11.0
> > rel/v1.10.0
> > rel/v1.9.2
> > rel/v1.9.1
> > rel/v1.9.0
> > rel/v1.8.0
> > rel/v1.7.0
> > rel/v1.6.0
> > rel/v1.5.0
> > rel/v1.4.0
> > rel/v1.3.0
> > rel/v1.2.1
> > rel/v1.2.0
> > rel/v1.1.1
> > rel/v1.1.0
> > rel/v1.0.0-incubating
> > rel/v1.0.0-incubating.M3
> > rel/v1.0.0-incubating.M2
> > rel/v1.0.0-incubating.M1
> >
> > I propose a one-time cleanup to DELETE all other tags, specifically:
> >
> > develop/highwater
> > modules-pre-merge
> > rel/v1.0.0-incubating.M1.RC1
> > rel/v1.0.0-incubating.M1.RC2
> > rel/v1.0.0-incubating.M2.RC1
> > rel/v1.0.0-incubating.M2.RC2
> > rel/v1.0.0-incubating.M3.RC1
> > rel/v1.0.0-incubating.M3.RC2
> > rel/v1.0.0-incubating.M3.RC3
> > rel/v1.0.0-incubating.M3.RC4
> > rel/v1.0.0-incubating.M3.RC5
> > rel/v1.0.0-incubating.M3.RC6
> > rel/v1.0.0-incubating.M3.RC7
> > rel/v1.0.0-incubating.RC1
> > rel/v1.0.0-incubating.RC2
> > rel/v1.1.0.RC1
> > rel/v1.1.0.RC2
> > rel/v1.1.0manualrev-2017-02-16
> > rel/v1.1.0manualrev-2017-10-19
> > rel/v1.1.1.RC1
> > rel/v1.1.1.RC2
> > rel/v1.10.0.1
> > rel/v1.10.0.1.RC1
> > rel/v1.10.0.2
> > rel/v1.10.0.RC1
> > rel/v1.10.0.RC2
> > rel/v1.11.0.1
> > rel/v1.11.0.2
> > rel/v1.11.0.23755
> > rel/v1.11.0.23755_2
> > rel/v1.11.0.23755_3
> > rel/v1.11.0.3
> > rel/v1.11.0.4
> > rel/v1.11.0.5
> > rel/v1.11.0.6
> > rel/v1.11.0.7
> > rel/v1.11.0.7565
> > rel/v1.11.0.8
> > rel/v1.11.0.RC1
> > rel/v1.11.0.RC2
> > rel/v1.11.0.RC3
> > rel/v1.11.0.RC4
> > rel/v1.12.0.1
> > rel/v1.12.0.1234
> > rel/v1.12.0.2
> > rel/v1.12.0.23755
> > rel/v1.12.0.3
> > rel/v1.12.0.4
> > rel/v1.12.0.5
> > rel/v1.12.0.6
> > rel/v1.12.0.RC1
> > rel/v1.12.0.RC2
> > rel/v1.12.0.RC3
> > rel/v1.12.0.RC4
> > rel/v1.14.0.23755
> > rel/v1.2.0.RC1
> > rel/v1.2.0.RC2
> > rel/v1.2.1.RC1
> > rel/v1.2.1.RC2
> > rel/v1.2.1.RC3
> > rel/v1.2.1.RC4
> > rel/v1.2.1manualrev-2017-10-19
> > rel/v1.3.0.RC1
> > rel/v1.3.0.RC2
> > rel/v1.3.0.RC3
> > rel/v1.3.0.RC4
> > rel/v1.4.0.RC1
> > rel/v1.4.0.RC2
> > rel/v1.5.0.RC1
> > rel/v1.5.0.RC2
> > rel/v1.6.0.RC1
> > rel/v1.7.0.RC1
> > rel/v1.7.0.RC2
> > rel/v1.8.0.RC1
> > rel/v1.8.0.RC2
> > rel/v1.9.0.1
> > rel/v1.9.0.1.RC1
> > rel/v1.9.0.2
> > rel/v1.9.0.RC1
> > rel/v1.9.0.RC2
> > rel/v1.9.0.RC3
> > rel/v1.9.0.RC4
> > rel/v1.9.1-nordix
> > rel/v1.9.1.RC1
> > rel/v1.9.1.RC2
> > rel/v1.9.1.RC3
> > rel/v1.9.2.RC1
> > sga2-core
> > v1.1.0manualrev-2017-10-19
> > v9.0.0-beta.1
> >
> --
> Ju@N
>
>

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Dave Barnes 
+1

On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols  wrote:

> Hi Donal, I can confirm that develop/highwater hasn't been updated in a
> year and is no longer in use by any pipelines (all pipelines use the last
> release tag as the benchmark baseline now).
>
> On 7/30/20, 5:48 AM, "Donal Evans"  wrote:
>
> I may be mistaken, but I think the develop/highwater tag was used by
> the geode-benchmarks project. Can we get confirmation that it's no longer
> in use?
>
> +1 conditional on that
>
> Get Outlook for Android<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Conichols%40vmware.com%7C9d3beabf432846c6345a08d83486d80f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317101044141000sdata=oH94Mya2EVyjt%2Bt%2FenrrGdsFZHYxAp17Ft6fqCI5cYQ%3Dreserved=0
> >
>
> 
> From: Ju@N 
> Sent: Thursday, July 30, 2020 3:10:44 AM
> To: dev@geode.apache.org 
> Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in
> geode repo
>
> +1
>
> On Thu 30 Jul 2020 at 08:21, Owen Nichols  wrote:
>
> > Tags in the rel/ namespace should be created by the Geode release
> manager
> > as part of an official Geode release only, yet we seem to have some
> extra
> > ones somehow.
> > Further, I don't see any value in keeping RC tags forever long after
> the
> > release is final.
> >
> > Please vote +1 in favor of trimming the current list of 110 tags
> down to
> > 20 to make it nice and easy for newcomers (as well as the rest of
> us) to
> > find and checkout a specific version of Geode; otherwise vote -1.
> If the
> > majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive
> and
> > delete the 90 unnecessary tags as detailed below.
> >
> > I propose to KEEP only the following tags, corresponding to official
> Geode
> > releases:
> >
> > rel/v1.12.0
> > rel/v1.11.0
> > rel/v1.10.0
> > rel/v1.9.2
> > rel/v1.9.1
> > rel/v1.9.0
> > rel/v1.8.0
> > rel/v1.7.0
> > rel/v1.6.0
> > rel/v1.5.0
> > rel/v1.4.0
> > rel/v1.3.0
> > rel/v1.2.1
> > rel/v1.2.0
> > rel/v1.1.1
> > rel/v1.1.0
> > rel/v1.0.0-incubating
> > rel/v1.0.0-incubating.M3
> > rel/v1.0.0-incubating.M2
> > rel/v1.0.0-incubating.M1
> >
> > I propose a one-time cleanup to DELETE all other tags, specifically:
> >
> > develop/highwater
> > modules-pre-merge
> > rel/v1.0.0-incubating.M1.RC1
> > rel/v1.0.0-incubating.M1.RC2
> > rel/v1.0.0-incubating.M2.RC1
> > rel/v1.0.0-incubating.M2.RC2
> > rel/v1.0.0-incubating.M3.RC1
> > rel/v1.0.0-incubating.M3.RC2
> > rel/v1.0.0-incubating.M3.RC3
> > rel/v1.0.0-incubating.M3.RC4
> > rel/v1.0.0-incubating.M3.RC5
> > rel/v1.0.0-incubating.M3.RC6
> > rel/v1.0.0-incubating.M3.RC7
> > rel/v1.0.0-incubating.RC1
> > rel/v1.0.0-incubating.RC2
> > rel/v1.1.0.RC1
> > rel/v1.1.0.RC2
> > rel/v1.1.0manualrev-2017-02-16
> > rel/v1.1.0manualrev-2017-10-19
> > rel/v1.1.1.RC1
> > rel/v1.1.1.RC2
> > rel/v1.10.0.1
> > rel/v1.10.0.1.RC1
> > rel/v1.10.0.2
> > rel/v1.10.0.RC1
> > rel/v1.10.0.RC2
> > rel/v1.11.0.1
> > rel/v1.11.0.2
> > rel/v1.11.0.23755
> > rel/v1.11.0.23755_2
> > rel/v1.11.0.23755_3
> > rel/v1.11.0.3
> > rel/v1.11.0.4
> > rel/v1.11.0.5
> > rel/v1.11.0.6
> > rel/v1.11.0.7
> > rel/v1.11.0.7565
> > rel/v1.11.0.8
> > rel/v1.11.0.RC1
> > rel/v1.11.0.RC2
> > rel/v1.11.0.RC3
> > rel/v1.11.0.RC4
> > rel/v1.12.0.1
> > rel/v1.12.0.1234
> > rel/v1.12.0.2
> > rel/v1.12.0.23755
> > rel/v1.12.0.3
> > rel/v1.12.0.4
> > rel/v1.12.0.5
> > rel/v1.12.0.6
> > rel/v1.12.0.RC1
> > rel/v1.12.0.RC2
> > rel/v1.12.0.RC3
> > rel/v1.12.0.RC4
> > rel/v1.14.0.23755
> > rel/v1.2.0.RC1
> > rel/v1.2.0.RC2
> > rel/v1.2.1.RC1
> > rel/v1.2.1.RC2
> > rel/v1.2.1.RC3
> > rel/v1.2.1.RC4
> > rel/v1.2.1manualrev-2017-10-19
> > rel/v1.3.0.RC1
> > rel/v1.3.0.RC2
> > rel/v1.3.0.RC3
> > rel/v1.3.0.RC4
> > rel/v1.4.0.RC1
> > rel/v1.4.0.RC2
> > rel/v1.5.0.RC1
> > rel/v1.5.0.RC2
> > rel/v1.6.0.RC1
> > rel/v1.7.0.RC1
> > rel/v1.7.0.RC2
> > rel/v1.8.0.RC1
> > rel/v1.8.0.RC2
> > rel/v1.9.0.1
> > rel/v1.9.0.1.RC1
> > rel/v1.9.0.2
> > rel/v1.9.0.RC1
> > rel/v1.9.0.RC2
> > rel/v1.9.0.RC3
> > rel/v1.9.0.RC4
> > rel/v1.9.1-nordix
> > rel/v1.9.1.RC1
> > rel/v1.9.1.RC2
> > rel/v1.9.1.RC3
> > rel/v1.9.2.RC1
> > sga2-core
> > v1.1.0manualrev-2017-10-19
> > v9.0.0-beta.1
> >
> --
> Ju@N
>
>

Re: [PROPOSAL] Postpone Geode 1.14

2020-07-30 Thread Darrel Schneider 
+1

From: Alexander Murmann 
Sent: Tuesday, July 28, 2020 4:34 PM
To: dev@geode.apache.org 
Subject: [PROPOSAL] Postpone Geode 1.14

Hi all,

As mentioned on the previous discuss thread, I propose to hold off cutting
1.14 until we have shipped 1.13.

Once we have shipped 1.13, we should discuss when we want to cut the 1.14
release. The actual ship date for Geode 1.13 is important information for
that conversation. Thus we cannot have that conversation before then.

Re: [PROPOSAL] Postpone Geode 1.14

2020-07-30 Thread Alexander Murmann 
Mark, that's a great point! I'll give everyone till tomorrow to contribute
their opinion on this thread and then inform the user list.

Thanks!

On Wed, Jul 29, 2020 at 1:35 PM Mark Bretl  wrote:

> +1
>
> Should we need to drop a line to user@geode or is communicating on this
> list enough once decided?
>
> --Mark
>
> On Wed, Jul 29, 2020 at 7:05 AM Joris Melchior 
> wrote:
>
> > +1
> >
> > On 2020-07-28, 7:34 PM, "Alexander Murmann" 
> wrote:
> >
> > Hi all,
> >
> > As mentioned on the previous discuss thread, I propose to hold off
> > cutting
> > 1.14 until we have shipped 1.13.
> >
> > Once we have shipped 1.13, we should discuss when we want to cut the
> > 1.14
> > release. The actual ship date for Geode 1.13 is important information
> > for
> > that conversation. Thus we cannot have that conversation before then.
> >
> >
>

Re: Review needed for c++ client ticket

2020-07-30 Thread Jacob Barrett 
The PR needs tests.

> On Jul 30, 2020, at 7:38 AM, Blake Bender  wrote:
> 
> Hi Alberto,
> 
> I've reached out to Jake to approve his review, then I'll merge this for you. 
>  Sorry for the delay.
> 
> Thanks,
> 
> Blake
> 
> 
> On 7/23/20, 3:08 AM, "Alberto Bustamante Reyes" 
>  wrote:
> 
>Hi,
> 
>Could someone please take a look at this c++ client PR? 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Fpull%2F628data=02%7C01%7Cjabarrett%40vmware.com%7Ccbc6d0b381de427f3fdb08d834964ef2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317167456674650sdata=1J8U%2FX4M7ghXIbSpy4VCQPizCdOIbnKNAz6RUbfasLo%3Dreserved=0
> 
>It solves a problem reported in the users list: 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fthread%2Fgajd4ok65w227fhldata=02%7C01%7Cjabarrett%40vmware.com%7Ccbc6d0b381de427f3fdb08d834964ef2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317167456674650sdata=dB%2BSWA%2FpGC%2F3ZVi0k6msa4B6l6XjiqD7QKGOMXzHERE%3Dreserved=0
> 
>Thanks,
> 
>Alberto B.
> 
>

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Owen Nichols 
Hi Donal, I can confirm that develop/highwater hasn't been updated in a year 
and is no longer in use by any pipelines (all pipelines use the last release 
tag as the benchmark baseline now).

On 7/30/20, 5:48 AM, "Donal Evans"  wrote:

I may be mistaken, but I think the develop/highwater tag was used by the 
geode-benchmarks project. Can we get confirmation that it's no longer in use?

+1 conditional on that

Get Outlook for 
Android


From: Ju@N 
Sent: Thursday, July 30, 2020 3:10:44 AM
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in 
geode repo

+1

On Thu 30 Jul 2020 at 08:21, Owen Nichols  wrote:

> Tags in the rel/ namespace should be created by the Geode release manager
> as part of an official Geode release only, yet we seem to have some extra
> ones somehow.
> Further, I don't see any value in keeping RC tags forever long after the
> release is final.
>
> Please vote +1 in favor of trimming the current list of 110 tags down to
> 20 to make it nice and easy for newcomers (as well as the rest of us) to
> find and checkout a specific version of Geode; otherwise vote -1.  If the
> majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive and
> delete the 90 unnecessary tags as detailed below.
>
> I propose to KEEP only the following tags, corresponding to official Geode
> releases:
>
> rel/v1.12.0
> rel/v1.11.0
> rel/v1.10.0
> rel/v1.9.2
> rel/v1.9.1
> rel/v1.9.0
> rel/v1.8.0
> rel/v1.7.0
> rel/v1.6.0
> rel/v1.5.0
> rel/v1.4.0
> rel/v1.3.0
> rel/v1.2.1
> rel/v1.2.0
> rel/v1.1.1
> rel/v1.1.0
> rel/v1.0.0-incubating
> rel/v1.0.0-incubating.M3
> rel/v1.0.0-incubating.M2
> rel/v1.0.0-incubating.M1
>
> I propose a one-time cleanup to DELETE all other tags, specifically:
>
> develop/highwater
> modules-pre-merge
> rel/v1.0.0-incubating.M1.RC1
> rel/v1.0.0-incubating.M1.RC2
> rel/v1.0.0-incubating.M2.RC1
> rel/v1.0.0-incubating.M2.RC2
> rel/v1.0.0-incubating.M3.RC1
> rel/v1.0.0-incubating.M3.RC2
> rel/v1.0.0-incubating.M3.RC3
> rel/v1.0.0-incubating.M3.RC4
> rel/v1.0.0-incubating.M3.RC5
> rel/v1.0.0-incubating.M3.RC6
> rel/v1.0.0-incubating.M3.RC7
> rel/v1.0.0-incubating.RC1
> rel/v1.0.0-incubating.RC2
> rel/v1.1.0.RC1
> rel/v1.1.0.RC2
> rel/v1.1.0manualrev-2017-02-16
> rel/v1.1.0manualrev-2017-10-19
> rel/v1.1.1.RC1
> rel/v1.1.1.RC2
> rel/v1.10.0.1
> rel/v1.10.0.1.RC1
> rel/v1.10.0.2
> rel/v1.10.0.RC1
> rel/v1.10.0.RC2
> rel/v1.11.0.1
> rel/v1.11.0.2
> rel/v1.11.0.23755
> rel/v1.11.0.23755_2
> rel/v1.11.0.23755_3
> rel/v1.11.0.3
> rel/v1.11.0.4
> rel/v1.11.0.5
> rel/v1.11.0.6
> rel/v1.11.0.7
> rel/v1.11.0.7565
> rel/v1.11.0.8
> rel/v1.11.0.RC1
> rel/v1.11.0.RC2
> rel/v1.11.0.RC3
> rel/v1.11.0.RC4
> rel/v1.12.0.1
> rel/v1.12.0.1234
> rel/v1.12.0.2
> rel/v1.12.0.23755
> rel/v1.12.0.3
> rel/v1.12.0.4
> rel/v1.12.0.5
> rel/v1.12.0.6
> rel/v1.12.0.RC1
> rel/v1.12.0.RC2
> rel/v1.12.0.RC3
> rel/v1.12.0.RC4
> rel/v1.14.0.23755
> rel/v1.2.0.RC1
> rel/v1.2.0.RC2
> rel/v1.2.1.RC1
> rel/v1.2.1.RC2
> rel/v1.2.1.RC3
> rel/v1.2.1.RC4
> rel/v1.2.1manualrev-2017-10-19
> rel/v1.3.0.RC1
> rel/v1.3.0.RC2
> rel/v1.3.0.RC3
> rel/v1.3.0.RC4
> rel/v1.4.0.RC1
> rel/v1.4.0.RC2
> rel/v1.5.0.RC1
> rel/v1.5.0.RC2
> rel/v1.6.0.RC1
> rel/v1.7.0.RC1
> rel/v1.7.0.RC2
> rel/v1.8.0.RC1
> rel/v1.8.0.RC2
> rel/v1.9.0.1
> rel/v1.9.0.1.RC1
> rel/v1.9.0.2
> rel/v1.9.0.RC1
> rel/v1.9.0.RC2
> rel/v1.9.0.RC3
> rel/v1.9.0.RC4
> rel/v1.9.1-nordix
> rel/v1.9.1.RC1
> rel/v1.9.1.RC2
> rel/v1.9.1.RC3
> rel/v1.9.2.RC1
> sga2-core
> v1.1.0manualrev-2017-10-19
> v9.0.0-beta.1
>
--
Ju@N

Re: [VOTE] change Default branch for geode-examples to 'develop'

2020-07-30 Thread Blake Bender 
FWIW, Geode Native works around this by not keeping a separate examples repo at 
all.  To build our examples, you *must* build your own Geode Native 
"installation," which includes the examples tree, or download the desired 
tarball/zip file from our GitHub releases.

I’m pretty much agnostic as to which way we should go for any particular 
repository, which is why I wrote "remove or rename" in the title of GEODE-8335. 
 Let's do the right thing for each repo, but not expend a ton of brain power on 
it.  I brought this up as a *small* gesture we should make in the name of 
kindness, not a large effort.

Thanks,

Blake
 

On 7/18/20, 2:42 AM, "Owen Nichols"  wrote:

Voting Results:
+1: 5 votes 
 0: 0 votes 
-1: 1 vote

The voting is successful by majority vote.  INFRA has completed the 
requested change and git clone g...@github.com:apache/geode-examples.git now 
checks out develop, making geode-examples consistent with all other geode- 
projects, and clearing the way to eliminate master from all projects if @Blake 
or anyone else would like to move forward on that.

Although it didn't seem to sway anyone else, let's still attempt to 
discuss/address @Anthony's concern that develop doesn't pair well with released 
versions of Geode.

Maybe the brew install + git clone workflow is not how we want to introduce 
an application developer to Geode.  We could suggest: if cloning from git, 
clone everything from git; if using released artifacts, use release artifacts 
for everything.  If mix-n-match is necessary, the README.md could explain how 
to check out the correct branch or tag (or specify the Geode version parameter 
in the gradle command) to match the installed version of Geode.

It's important and fundamental for application developers to be aware that 
client version must be <= server version, so perhaps it's beneficial to 
document that from the beginning.

Another idea might be improving the error message when the client version 
is too new?

We could also modify the release scripts to substitute the latest release 
version into the README as part of the release process, to keep the 
out-of-the-box experience as simple as copy-and-pasting a gradle command from 
the README.

@Anthony I'd be happy to pair with you on updating the README or any other 
scripts/documentation.

If anyone else has thoughts or ideas, please chime in.

On 7/14/20, 7:16 AM, "Anthony Baker"  wrote:

Consider the use case of an application developer who wants to run 
geode-examples against the latest geode release:

1) brew install apache-geode
2) git clone geode-examples
3) Get some runtime errors because geode-examples won’t connect to a 
previous geode release

At this point, you have to do some detective work to either download 
the geode-examples from the corresponding source release or switch over to the 
appropriate git tag.

I think there’s value in maintaining a default branch of geode-examples 
that tracks the latest release.

Anthony


> On Jul 9, 2020, at 9:39 PM, Owen Nichols  wrote:
> 
> A fresh checkout of geode and all but one geode- 
repos checks out develop as the Default branch.
> 
> The lone exception is geode-examples.  Please vote +1 if you are in 
favor of changing its Default branch to develop for consistency with the other 
repos and other reasons as per recent discussion[1].
> 
> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cbblake%40vmware.com%7Cb2eb424632174cd66c2408d82afee313%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637306621505139591sdata=DWUOSFvwEnJDJytU7qSjrzFEzR8gzjIm96pXAOqnxUQ%3Dreserved=0

Re: Review needed for c++ client ticket

2020-07-30 Thread Blake Bender 
Hi Alberto,

I've reached out to Jake to approve his review, then I'll merge this for you.  
Sorry for the delay.

Thanks,

Blake


On 7/23/20, 3:08 AM, "Alberto Bustamante Reyes" 
 wrote:

Hi,

Could someone please take a look at this c++ client PR? 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Fpull%2F628data=02%7C01%7Cbblake%40vmware.com%7C642d90cada944bd7e52508d82ef047da%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637310956821127150sdata=BTTTnQRvOyKZoYFSePHmVMJccTME1oq1KerC6V62DO0%3Dreserved=0

It solves a problem reported in the users list: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fthread%2Fgajd4ok65w227fhldata=02%7C01%7Cbblake%40vmware.com%7C642d90cada944bd7e52508d82ef047da%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637310956821127150sdata=QNPJPFtP30SzadDoTgFCDteSqX4u8UGR%2BnuWMcX4OoU%3Dreserved=0

Thanks,

Alberto B.

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Donal Evans 
I may be mistaken, but I think the develop/highwater tag was used by the 
geode-benchmarks project. Can we get confirmation that it's no longer in use?

+1 conditional on that

Get Outlook for Android


From: Ju@N 
Sent: Thursday, July 30, 2020 3:10:44 AM
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode 
repo

+1

On Thu 30 Jul 2020 at 08:21, Owen Nichols  wrote:

> Tags in the rel/ namespace should be created by the Geode release manager
> as part of an official Geode release only, yet we seem to have some extra
> ones somehow.
> Further, I don't see any value in keeping RC tags forever long after the
> release is final.
>
> Please vote +1 in favor of trimming the current list of 110 tags down to
> 20 to make it nice and easy for newcomers (as well as the rest of us) to
> find and checkout a specific version of Geode; otherwise vote -1.  If the
> majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive and
> delete the 90 unnecessary tags as detailed below.
>
> I propose to KEEP only the following tags, corresponding to official Geode
> releases:
>
> rel/v1.12.0
> rel/v1.11.0
> rel/v1.10.0
> rel/v1.9.2
> rel/v1.9.1
> rel/v1.9.0
> rel/v1.8.0
> rel/v1.7.0
> rel/v1.6.0
> rel/v1.5.0
> rel/v1.4.0
> rel/v1.3.0
> rel/v1.2.1
> rel/v1.2.0
> rel/v1.1.1
> rel/v1.1.0
> rel/v1.0.0-incubating
> rel/v1.0.0-incubating.M3
> rel/v1.0.0-incubating.M2
> rel/v1.0.0-incubating.M1
>
> I propose a one-time cleanup to DELETE all other tags, specifically:
>
> develop/highwater
> modules-pre-merge
> rel/v1.0.0-incubating.M1.RC1
> rel/v1.0.0-incubating.M1.RC2
> rel/v1.0.0-incubating.M2.RC1
> rel/v1.0.0-incubating.M2.RC2
> rel/v1.0.0-incubating.M3.RC1
> rel/v1.0.0-incubating.M3.RC2
> rel/v1.0.0-incubating.M3.RC3
> rel/v1.0.0-incubating.M3.RC4
> rel/v1.0.0-incubating.M3.RC5
> rel/v1.0.0-incubating.M3.RC6
> rel/v1.0.0-incubating.M3.RC7
> rel/v1.0.0-incubating.RC1
> rel/v1.0.0-incubating.RC2
> rel/v1.1.0.RC1
> rel/v1.1.0.RC2
> rel/v1.1.0manualrev-2017-02-16
> rel/v1.1.0manualrev-2017-10-19
> rel/v1.1.1.RC1
> rel/v1.1.1.RC2
> rel/v1.10.0.1
> rel/v1.10.0.1.RC1
> rel/v1.10.0.2
> rel/v1.10.0.RC1
> rel/v1.10.0.RC2
> rel/v1.11.0.1
> rel/v1.11.0.2
> rel/v1.11.0.23755
> rel/v1.11.0.23755_2
> rel/v1.11.0.23755_3
> rel/v1.11.0.3
> rel/v1.11.0.4
> rel/v1.11.0.5
> rel/v1.11.0.6
> rel/v1.11.0.7
> rel/v1.11.0.7565
> rel/v1.11.0.8
> rel/v1.11.0.RC1
> rel/v1.11.0.RC2
> rel/v1.11.0.RC3
> rel/v1.11.0.RC4
> rel/v1.12.0.1
> rel/v1.12.0.1234
> rel/v1.12.0.2
> rel/v1.12.0.23755
> rel/v1.12.0.3
> rel/v1.12.0.4
> rel/v1.12.0.5
> rel/v1.12.0.6
> rel/v1.12.0.RC1
> rel/v1.12.0.RC2
> rel/v1.12.0.RC3
> rel/v1.12.0.RC4
> rel/v1.14.0.23755
> rel/v1.2.0.RC1
> rel/v1.2.0.RC2
> rel/v1.2.1.RC1
> rel/v1.2.1.RC2
> rel/v1.2.1.RC3
> rel/v1.2.1.RC4
> rel/v1.2.1manualrev-2017-10-19
> rel/v1.3.0.RC1
> rel/v1.3.0.RC2
> rel/v1.3.0.RC3
> rel/v1.3.0.RC4
> rel/v1.4.0.RC1
> rel/v1.4.0.RC2
> rel/v1.5.0.RC1
> rel/v1.5.0.RC2
> rel/v1.6.0.RC1
> rel/v1.7.0.RC1
> rel/v1.7.0.RC2
> rel/v1.8.0.RC1
> rel/v1.8.0.RC2
> rel/v1.9.0.1
> rel/v1.9.0.1.RC1
> rel/v1.9.0.2
> rel/v1.9.0.RC1
> rel/v1.9.0.RC2
> rel/v1.9.0.RC3
> rel/v1.9.0.RC4
> rel/v1.9.1-nordix
> rel/v1.9.1.RC1
> rel/v1.9.1.RC2
> rel/v1.9.1.RC3
> rel/v1.9.2.RC1
> sga2-core
> v1.1.0manualrev-2017-10-19
> v9.0.0-beta.1
>
--
Ju@N

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Ju@N 
+1

On Thu 30 Jul 2020 at 08:21, Owen Nichols  wrote:

> Tags in the rel/ namespace should be created by the Geode release manager
> as part of an official Geode release only, yet we seem to have some extra
> ones somehow.
> Further, I don't see any value in keeping RC tags forever long after the
> release is final.
>
> Please vote +1 in favor of trimming the current list of 110 tags down to
> 20 to make it nice and easy for newcomers (as well as the rest of us) to
> find and checkout a specific version of Geode; otherwise vote -1.  If the
> majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive and
> delete the 90 unnecessary tags as detailed below.
>
> I propose to KEEP only the following tags, corresponding to official Geode
> releases:
>
> rel/v1.12.0
> rel/v1.11.0
> rel/v1.10.0
> rel/v1.9.2
> rel/v1.9.1
> rel/v1.9.0
> rel/v1.8.0
> rel/v1.7.0
> rel/v1.6.0
> rel/v1.5.0
> rel/v1.4.0
> rel/v1.3.0
> rel/v1.2.1
> rel/v1.2.0
> rel/v1.1.1
> rel/v1.1.0
> rel/v1.0.0-incubating
> rel/v1.0.0-incubating.M3
> rel/v1.0.0-incubating.M2
> rel/v1.0.0-incubating.M1
>
> I propose a one-time cleanup to DELETE all other tags, specifically:
>
> develop/highwater
> modules-pre-merge
> rel/v1.0.0-incubating.M1.RC1
> rel/v1.0.0-incubating.M1.RC2
> rel/v1.0.0-incubating.M2.RC1
> rel/v1.0.0-incubating.M2.RC2
> rel/v1.0.0-incubating.M3.RC1
> rel/v1.0.0-incubating.M3.RC2
> rel/v1.0.0-incubating.M3.RC3
> rel/v1.0.0-incubating.M3.RC4
> rel/v1.0.0-incubating.M3.RC5
> rel/v1.0.0-incubating.M3.RC6
> rel/v1.0.0-incubating.M3.RC7
> rel/v1.0.0-incubating.RC1
> rel/v1.0.0-incubating.RC2
> rel/v1.1.0.RC1
> rel/v1.1.0.RC2
> rel/v1.1.0manualrev-2017-02-16
> rel/v1.1.0manualrev-2017-10-19
> rel/v1.1.1.RC1
> rel/v1.1.1.RC2
> rel/v1.10.0.1
> rel/v1.10.0.1.RC1
> rel/v1.10.0.2
> rel/v1.10.0.RC1
> rel/v1.10.0.RC2
> rel/v1.11.0.1
> rel/v1.11.0.2
> rel/v1.11.0.23755
> rel/v1.11.0.23755_2
> rel/v1.11.0.23755_3
> rel/v1.11.0.3
> rel/v1.11.0.4
> rel/v1.11.0.5
> rel/v1.11.0.6
> rel/v1.11.0.7
> rel/v1.11.0.7565
> rel/v1.11.0.8
> rel/v1.11.0.RC1
> rel/v1.11.0.RC2
> rel/v1.11.0.RC3
> rel/v1.11.0.RC4
> rel/v1.12.0.1
> rel/v1.12.0.1234
> rel/v1.12.0.2
> rel/v1.12.0.23755
> rel/v1.12.0.3
> rel/v1.12.0.4
> rel/v1.12.0.5
> rel/v1.12.0.6
> rel/v1.12.0.RC1
> rel/v1.12.0.RC2
> rel/v1.12.0.RC3
> rel/v1.12.0.RC4
> rel/v1.14.0.23755
> rel/v1.2.0.RC1
> rel/v1.2.0.RC2
> rel/v1.2.1.RC1
> rel/v1.2.1.RC2
> rel/v1.2.1.RC3
> rel/v1.2.1.RC4
> rel/v1.2.1manualrev-2017-10-19
> rel/v1.3.0.RC1
> rel/v1.3.0.RC2
> rel/v1.3.0.RC3
> rel/v1.3.0.RC4
> rel/v1.4.0.RC1
> rel/v1.4.0.RC2
> rel/v1.5.0.RC1
> rel/v1.5.0.RC2
> rel/v1.6.0.RC1
> rel/v1.7.0.RC1
> rel/v1.7.0.RC2
> rel/v1.8.0.RC1
> rel/v1.8.0.RC2
> rel/v1.9.0.1
> rel/v1.9.0.1.RC1
> rel/v1.9.0.2
> rel/v1.9.0.RC1
> rel/v1.9.0.RC2
> rel/v1.9.0.RC3
> rel/v1.9.0.RC4
> rel/v1.9.1-nordix
> rel/v1.9.1.RC1
> rel/v1.9.1.RC2
> rel/v1.9.1.RC3
> rel/v1.9.2.RC1
> sga2-core
> v1.1.0manualrev-2017-10-19
> v9.0.0-beta.1
>
-- 
Ju@N

[PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Owen Nichols 
Tags in the rel/ namespace should be created by the Geode release manager as 
part of an official Geode release only, yet we seem to have some extra ones 
somehow.
Further, I don't see any value in keeping RC tags forever long after the 
release is final.

Please vote +1 in favor of trimming the current list of 110 tags down to 20 to 
make it nice and easy for newcomers (as well as the rest of us) to find and 
checkout a specific version of Geode; otherwise vote -1.  If the majority vote 
is +1 at 3PM PDT Fri Aug 7, I will proceed to archive and delete the 90 
unnecessary tags as detailed below.

I propose to KEEP only the following tags, corresponding to official Geode 
releases:

rel/v1.12.0
rel/v1.11.0
rel/v1.10.0
rel/v1.9.2
rel/v1.9.1
rel/v1.9.0
rel/v1.8.0
rel/v1.7.0
rel/v1.6.0
rel/v1.5.0
rel/v1.4.0
rel/v1.3.0
rel/v1.2.1
rel/v1.2.0
rel/v1.1.1
rel/v1.1.0
rel/v1.0.0-incubating
rel/v1.0.0-incubating.M3
rel/v1.0.0-incubating.M2
rel/v1.0.0-incubating.M1

I propose a one-time cleanup to DELETE all other tags, specifically:

develop/highwater
modules-pre-merge
rel/v1.0.0-incubating.M1.RC1
rel/v1.0.0-incubating.M1.RC2
rel/v1.0.0-incubating.M2.RC1
rel/v1.0.0-incubating.M2.RC2
rel/v1.0.0-incubating.M3.RC1
rel/v1.0.0-incubating.M3.RC2
rel/v1.0.0-incubating.M3.RC3
rel/v1.0.0-incubating.M3.RC4
rel/v1.0.0-incubating.M3.RC5
rel/v1.0.0-incubating.M3.RC6
rel/v1.0.0-incubating.M3.RC7
rel/v1.0.0-incubating.RC1
rel/v1.0.0-incubating.RC2
rel/v1.1.0.RC1
rel/v1.1.0.RC2
rel/v1.1.0manualrev-2017-02-16
rel/v1.1.0manualrev-2017-10-19
rel/v1.1.1.RC1
rel/v1.1.1.RC2
rel/v1.10.0.1
rel/v1.10.0.1.RC1
rel/v1.10.0.2
rel/v1.10.0.RC1
rel/v1.10.0.RC2
rel/v1.11.0.1
rel/v1.11.0.2
rel/v1.11.0.23755
rel/v1.11.0.23755_2
rel/v1.11.0.23755_3
rel/v1.11.0.3
rel/v1.11.0.4
rel/v1.11.0.5
rel/v1.11.0.6
rel/v1.11.0.7
rel/v1.11.0.7565
rel/v1.11.0.8
rel/v1.11.0.RC1
rel/v1.11.0.RC2
rel/v1.11.0.RC3
rel/v1.11.0.RC4
rel/v1.12.0.1
rel/v1.12.0.1234
rel/v1.12.0.2
rel/v1.12.0.23755
rel/v1.12.0.3
rel/v1.12.0.4
rel/v1.12.0.5
rel/v1.12.0.6
rel/v1.12.0.RC1
rel/v1.12.0.RC2
rel/v1.12.0.RC3
rel/v1.12.0.RC4
rel/v1.14.0.23755
rel/v1.2.0.RC1
rel/v1.2.0.RC2
rel/v1.2.1.RC1
rel/v1.2.1.RC2
rel/v1.2.1.RC3
rel/v1.2.1.RC4
rel/v1.2.1manualrev-2017-10-19
rel/v1.3.0.RC1
rel/v1.3.0.RC2
rel/v1.3.0.RC3
rel/v1.3.0.RC4
rel/v1.4.0.RC1
rel/v1.4.0.RC2
rel/v1.5.0.RC1
rel/v1.5.0.RC2
rel/v1.6.0.RC1
rel/v1.7.0.RC1
rel/v1.7.0.RC2
rel/v1.8.0.RC1
rel/v1.8.0.RC2
rel/v1.9.0.1
rel/v1.9.0.1.RC1
rel/v1.9.0.2
rel/v1.9.0.RC1
rel/v1.9.0.RC2
rel/v1.9.0.RC3
rel/v1.9.0.RC4
rel/v1.9.1-nordix
rel/v1.9.1.RC1
rel/v1.9.1.RC2
rel/v1.9.1.RC3
rel/v1.9.2.RC1
sga2-core
v1.1.0manualrev-2017-10-19
v9.0.0-beta.1