one needs more information.
Regards
Nabarun
From: Alexander Murmann
Sent: Wednesday, January 6, 2021 7:39 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi team!
If I am reading the silence correctly as silent approva
: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi team!
If I am reading the silence correctly as silent approval, can everyone please
start to add the blocks-1.14.0 label to all tickets we should consider as
release blockers?
I also would encourage us to not remove the label when we
t behavior.
From: Alexander Murmann
Sent: Tuesday, January 5, 2021 08:34
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
I agree with Jianxia that a dashboard would be helpful.
Not every bug that affects a release should necessarily be a release blocker.
Factors like lo
ppropriate.
How does that sound?
From: Jacob Barrett
Sent: Monday, January 4, 2021 16:40
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
> On Jan 4, 2021, at 3:42 PM, Owen Nichols wrote:
>
> How to tell whether develop is stable?
Same way
> On Jan 4, 2021, at 3:42 PM, Owen Nichols wrote:
>
> How to tell whether develop is stable?
Same way we tell if a release branch is stable.
Listen, cutting a release branch from the develop branch shouldn’t result in
weeks worth of stabilization of the release branch. That is a smell that
ell whether develop is stable?
>
> From: Jacob Barrett
> Date: Monday, January 4, 2021 at 8:59 AM
> To: dev@geode.apache.org
> Subject: Re: [DISCUSS] Geode 1.14
> Keep develop stable, cut when we want to release. If develop isn’t stable
> we don’t cut until it is. There is
How to tell whether develop is stable?
From: Jacob Barrett
Date: Monday, January 4, 2021 at 8:59 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Keep develop stable, cut when we want to release. If develop isn’t stable we
don’t cut until it is. There is no reason we can’t keep
Let’s regroup next month and
try to clarify exactly which GEODE Jira tickets we need to focus on to make
sure 1.14 is our best release.
From: Owen Nichols
Date: Tuesday, December 1, 2020 at 12:26 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.1
ira tickets we need to focus on to
> make sure 1.14 is our best release.
>
> From: Owen Nichols
>Date: Tuesday, December 1, 2020 at 12:26 PM
>To: dev@geode.apache.org
>Subject: Re: [DISCUSS] Geode 1.14
>If someone wants to propose
s regroup next month and
try to clarify exactly which GEODE Jira tickets we need to focus on to make
sure 1.14 is our best release.
From: Owen Nichols
Date: Tuesday, December 1, 2020 at 12:26 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
ut. Let’s regroup next month and
try to clarify exactly which GEODE Jira tickets we need to focus on to make
sure 1.14 is our best release.
From: Owen Nichols
Date: Tuesday, December 1, 2020 at 12:26 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
If someon
@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
If someone wants to propose a list of must-fix Jira tickets before we can cut
the branch, I see that as a shift from a time-based to feature-based branch-cut
strategy. Might be fun to try?
Given the distributed nature of the Geode community, picking
ughts?
From: Jens Deppe
Sent: Wednesday, November 25, 2020 20:11
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi Owen,
Thanks for starting this conversation and especially for volunteering as
Release Manager!
Since we're already a couple o
core application?
From: Alexander Murmann
Date: Monday, November 30, 2020 at 2:57 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi all,
Thanks, Owen for reminding us all of this topic!
I wonder how we feel about the state of develop right now. If we cut 1.14 right
now, it will
. Same effort, but a
more-quickly-stable release branch.
-Robert
From: Alexander Murmann
Date: Monday, November 30, 2020 at 11:57 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi all,
Thanks, Owen for reminding us all of this topic!
I wonder how we feel about the state of develop
ughts?
From: Jens Deppe
Sent: Wednesday, November 25, 2020 20:11
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Geode 1.14
Hi Owen,
Thanks for starting this conversation and especially for volunteering as
Release Manager!
Since we're already a couple o
Hi Owen,
Thanks for starting this conversation and especially for volunteering as
Release Manager!
Since we're already a couple of quarters 'behind', in terms of releases, I'd
prefer cutting the 1.14 branch ASAP. Leaving it until Feb means we'll have 9
months of changes to stabilize. How long
17 matches
Mail list logo
