Re: [PROPOSAL] Postpone Geode 1.14

[Owen Nichols]

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"  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 
Sent: Monday, August 3, 2020 09:59
To: 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"  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 
Sent: Thursday, July 30, 2020 13:47
To: dev@geode.apache.org 
    Subject: Re: [PROPOSAL] Postpone Geode 1.14

+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] Postpone Geode 1.14

[Michael Oleske]

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 
Sent: Monday, August 3, 2020 09:59
To: 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"  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 
Sent: Thursday, July 30, 2020 13:47
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] Postpone Geode 1.14

+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] Postpone Geode 1.14

[Mark Hanson]

+1 to Michael's suggestion.

On 7/31/20, 5:38 PM, "Michael Oleske"  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 
Sent: Thursday, July 30, 2020 13:47
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] Postpone Geode 1.14

+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] Postpone Geode 1.14

[Michael Oleske]

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 
Sent: Thursday, July 30, 2020 13:47
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] Postpone Geode 1.14

+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] Postpone Geode 1.14

[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] Postpone Geode 1.14

[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

[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: [PROPOSAL] Postpone Geode 1.14

[Mark Bretl]

+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] Postpone Geode 1.14

[Joris Melchior]

+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] Postpone Geode 1.14

[Dave Barnes]

+1

On Tue, Jul 28, 2020 at 5:05 PM Donal Evans  wrote:

> +1
> 
> From: Owen Nichols 
> Sent: Tuesday, July 28, 2020 4:38 PM
> To: Alexander Murmann ; dev@geode.apache.org <
> dev@geode.apache.org>
> Subject: Re: [PROPOSAL] Postpone Geode 1.14
>
> +1
>
>
> ---
> Sent from Workspace ONE Boxer<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=02%7C01%7Cdoevans%40vmware.com%7Ccd4d1f981e344957f92a08d8334f6516%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637315763386093818sdata=Ydv6m8%2F2p6c342hpTp3HStbMDCqD3M4xJfFLjeMc1ZM%3Dreserved=0
> >
>
> On July 28, 2020 at 4:34:55 PM PDT, 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] Postpone Geode 1.14

[Donal Evans]

+1

From: Owen Nichols 
Sent: Tuesday, July 28, 2020 4:38 PM
To: Alexander Murmann ; dev@geode.apache.org 

Subject: Re: [PROPOSAL] Postpone Geode 1.14

+1


---
Sent from Workspace ONE 
Boxer<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=02%7C01%7Cdoevans%40vmware.com%7Ccd4d1f981e344957f92a08d8334f6516%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637315763386093818sdata=Ydv6m8%2F2p6c342hpTp3HStbMDCqD3M4xJfFLjeMc1ZM%3Dreserved=0>

On July 28, 2020 at 4:34:55 PM PDT, 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] Postpone Geode 1.14

[Owen Nichols]

+1


---
Sent from Workspace ONE Boxer

On July 28, 2020 at 4:34:55 PM PDT, 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.

[PROPOSAL] Postpone Geode 1.14

[Alexander Murmann]

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.