Hi Michael, lack of replies may be simply due to not having shipped 1.13 yet.
Once it's in the rearview mirror, folks may be more in the frame of mind to
look back at it, perhaps as part of the already-proposed discussion ("Once we
have shipped 1.13, we should discuss when we want to cut the 1.14").
Traditionally Geode uses the [DISCUSS] email thread format to accommodate our
worldwide developer community. Looking forward to hearing your voice (and
hopefully many others) soon.
On 8/7/20, 12:00 PM, "Michael Oleske" <mole...@vmware.com> wrote:
I'm going to take the lack of replies as there are no plans for a
retrospective on this. If there is interest in doing this in the future, I'd
be happy to facilitate the discussion.
-michael
________________________________
From: Mark Hanson <hans...@vmware.com>
Sent: Monday, August 3, 2020 09:59
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: [PROPOSAL] Postpone Geode 1.14
+1 to Michael's suggestion.
On 7/31/20, 5:38 PM, "Michael Oleske" <mole...@vmware.com> wrote:
Is there plans as a community to do a postmortem or retrospective
around why the release is taking so long? If there is an understanding of
events that occurred to cause the long delay of Geode 1.13 to be released, that
would help inform decisions if processes should change or if the release
cadence should change (or both!)
-michael
________________________________
From: Xiaojian Zhou <zho...@vmware.com>
Sent: Thursday, July 30, 2020 13:47
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: [PROPOSAL] Postpone Geode 1.14
+1
On 7/29/20, 1:35 PM, "Mark Bretl" <mbr...@apache.org> 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
<jmelch...@vmware.com> wrote:
> +1
>
> On 2020-07-28, 7:34 PM, "Alexander Murmann" <amurm...@apache.org>
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.
>
>
