ng 1.13 now would effectively be seeing
> all
> > that work go to waste. It also wouldn't address the core issue that
> those
> > most heavily involved in the release process and in identifying and
> > addressing potential release blockers are in danger of being
release, and dropping 1.13 now would effectively be seeing
> all
> > that work go to waste. It also wouldn't address the core issue that
> those
> > most heavily involved in the release process and in identifying and
> > addressing potential release blockers
r of additional ones that we may not know about yet.
>
> From: Jacob Barrett
> Sent: Monday, July 20, 2020 9:38 AM
> To: dev@geode.apache.org
> Subject: Re: [Discuss] Cutting Geode 1.14
>
&
nd in identifying and
> addressing potential release blockers are in danger of being exhausted by
> the non-stop process of finding and fixing bugs in the release, since 1.14
> will have all of the same blockers that 1.13 currently has, plus an
> undetermined number of additional ones tha
M
To: dev@geode.apache.org
Subject: Re: [Discuss] Cutting Geode 1.14
Alternatively, why not abandon 1.13 and try again with 1.14?
> On Jul 20, 2020, at 9:21 AM, Alexander Murmann
wrote:
>
> Hi everyone,
>
> TL;DR: Let's discuss 1.14 once 1.13
ding and fixing bugs in the release, since 1.14 will have all of the
> same blockers that 1.13 currently has, plus an undetermined number of
> additional ones that we may not know about yet.
>
> From: Jacob Barrett
> Sent: Monday, July 20, 2
eode.apache.org
Subject: Re: [Discuss] Cutting Geode 1.14
Alternatively, why not abandon 1.13 and try again with 1.14?
> On Jul 20, 2020, at 9:21 AM, Alexander Murmann wrote:
>
> Hi everyone,
>
> TL;DR: Let's discuss 1.14 once 1.13 is out.
>
> If we stick to our cadenc
Playing devil's advocate here, but I think the reason we would not like to move
to 1.14 would be that we have a ton testing already in to quantify issues on
1.13 and 1.14 would be (a bit) of an unknown quantity. Further, the core issues
that we are waiting on for 1.13 are presumable 1.14 issues
Alternatively, why not abandon 1.13 and try again with 1.14?
> On Jul 20, 2020, at 9:21 AM, Alexander Murmann wrote:
>
> Hi everyone,
>
> TL;DR: Let's discuss 1.14 once 1.13 is out.
>
> If we stick to our cadence of cutting a release every 3 months and shipping
> it 1 month later, 1.14 is due
Hi everyone,
TL;DR: Let's discuss 1.14 once 1.13 is out.
If we stick to our cadence of cutting a release every 3 months and shipping
it 1 month later, 1.14 is due to be cut two weeks from today. However, we
haven't shipped 1.13 yet and are still struggling with some issues.
I suggest that we pos
10 matches
Mail list logo
