From: Anilkumar Gingade
Sent: Tuesday, January 4, 2022 07:09
To: dev@geode.apache.org
Subject: Re: [DISCUSS] proposal to pare down old-version testing
+1
Thanks for bringing this and taking care of this.
-Anil.
On 1/3/22, 10:41 AM, "Dan Smith" wrote:
.apache.org
Subject: Re: [DISCUSS] proposal to pare down old-version testing
+1
Thanks for bringing this and taking care of this.
-Anil.
On 1/3/22, 10:41 AM, "Dan Smith" wrote:
Looking at KnownVersion.java - we did make protocol changes in 1.12.1 and
1.13.2. So, my suggestion would
hat aren't the latest.
-Dan
From: Dan Smith
Sent: Monday, January 3, 2022 10:37 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] proposal to pare down old-version testing
+1 - this seems reasonable to me. If we do make a proto
AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] proposal to pare down old-version testing
+1 - this seems reasonable to me. If we do make a protocol change in a patch,
we could potentially keep around an older patch version just in that specific
case, but otherwise I think this makes sense.
8:53 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] proposal to pare down old-version testing
Interesting data point: 40% of maven central downloads last month were for
version 1.4.0. Of course those numbers can be easily skewed by CI bots, but
still!
@Owen, I think your suggestion nicely
Interesting data point: 40% of maven central downloads last month were for
version 1.4.0. Of course those numbers can be easily skewed by CI bots, but
still!
@Owen, I think your suggestion nicely improves practicality while continuing to
support strong compatibility. In many cases it’s quite a
Yes! This! 100%!
> On Dec 22, 2021, at 7:14 PM, Owen Nichols wrote:
>
> Since adopting our N-2 support policy, the list of released versions in
> /settings.gradle has ballooned to over 30 entries [1].
>
> CI tests use this list to confirm that we don’t break rolling upgrade ability
> or comp
Since adopting our N-2 support policy, the list of released versions in
/settings.gradle has ballooned to over 30 entries [1].
CI tests use this list to confirm that we don’t break rolling upgrade ability
or compatibility with older clients, but some of these tests don’t seem to
scale well: PR#
