You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Benjamin Lerer <bl...@apache.org> on 2021/12/14 09:20:36 UTC
[DISCUSS] Next release cut
Hi everybody,
I believe that we never really clarified when the next release should
happen. We agreed on a yearly frequency but did not go down on the details.
It might be worth it to clarify them so that we are sure that everybody is
on the same line.
We cut 4.0 in May and released it in July. It is difficult to plan for a
release date so we should probably agree on the cut date. One year after
4.0 that would make us cut the new branch in May.
Does it match your expectations or are there any concerns?
Re: [DISCUSS] Next release cut
Posted by Caleb Rackliffe <ca...@gmail.com>.
+1
On Mon, Jan 3, 2022 at 1:21 PM Brandon Williams <dr...@gmail.com> wrote:
> +1 to 4.1 in May.
>
> On Tue, Dec 14, 2021, 6:46 AM Mick Semb Wever <mc...@apache.org> wrote:
>
>> > We cut 4.0 in May and released it in July. It is difficult to plan for a
>> release date so we should probably agree on the cut date. One year after
>> 4.0 that would make us cut the new branch in May.
>>
>>
>> This makes sense to me. The time between each rc1 cut is the only
>> thing we control. We want the rc1 cut to GA published time frame to be
>> minimised (that is the goal of stable-trunk) but that it is a
>> variable, and not something we want to put pressure on or compromise.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
Re: [DISCUSS] Next release cut
Posted by Brandon Williams <dr...@gmail.com>.
+1 to 4.1 in May.
On Tue, Dec 14, 2021, 6:46 AM Mick Semb Wever <mc...@apache.org> wrote:
> > We cut 4.0 in May and released it in July. It is difficult to plan for a
> release date so we should probably agree on the cut date. One year after
> 4.0 that would make us cut the new branch in May.
>
>
> This makes sense to me. The time between each rc1 cut is the only
> thing we control. We want the rc1 cut to GA published time frame to be
> minimised (that is the goal of stable-trunk) but that it is a
> variable, and not something we want to put pressure on or compromise.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [DISCUSS] Next release cut
Posted by Joshua McKenzie <jm...@apache.org>.
+1 to 4.1 in May.
On Mon, Jan 3, 2022 at 12:58 PM David Capwell <dc...@apple.com> wrote:
> 4.1 target of may works for me, we may want to remove a few things in
> Config.java if not wrapped up on time (thinking track warnings and
> guardrails, though that should be handled by then)
>
> > On Dec 14, 2021, at 5:02 AM, Paulo Motta <pa...@gmail.com>
> wrote:
> >
> > +1 to cut 4.1 in May. It would be great to attain the yearly cut cadence
> if
> > possible.
> >
> > Em ter., 14 de dez. de 2021 às 09:45, Mick Semb Wever <mc...@apache.org>
> > escreveu:
> >
> >>> We cut 4.0 in May and released it in July. It is difficult to plan for
> a
> >> release date so we should probably agree on the cut date. One year after
> >> 4.0 that would make us cut the new branch in May.
> >>
> >>
> >> This makes sense to me. The time between each rc1 cut is the only
> >> thing we control. We want the rc1 cut to GA published time frame to be
> >> minimised (that is the goal of stable-trunk) but that it is a
> >> variable, and not something we want to put pressure on or compromise.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> >> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>
> >>
>
>
Re: [DISCUSS] Next release cut
Posted by David Capwell <dc...@apple.com>.
4.1 target of may works for me, we may want to remove a few things in Config.java if not wrapped up on time (thinking track warnings and guardrails, though that should be handled by then)
> On Dec 14, 2021, at 5:02 AM, Paulo Motta <pa...@gmail.com> wrote:
>
> +1 to cut 4.1 in May. It would be great to attain the yearly cut cadence if
> possible.
>
> Em ter., 14 de dez. de 2021 às 09:45, Mick Semb Wever <mc...@apache.org>
> escreveu:
>
>>> We cut 4.0 in May and released it in July. It is difficult to plan for a
>> release date so we should probably agree on the cut date. One year after
>> 4.0 that would make us cut the new branch in May.
>>
>>
>> This makes sense to me. The time between each rc1 cut is the only
>> thing we control. We want the rc1 cut to GA published time frame to be
>> minimised (that is the goal of stable-trunk) but that it is a
>> variable, and not something we want to put pressure on or compromise.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
Re: [DISCUSS] Next release cut
Posted by Paulo Motta <pa...@gmail.com>.
+1 to cut 4.1 in May. It would be great to attain the yearly cut cadence if
possible.
Em ter., 14 de dez. de 2021 às 09:45, Mick Semb Wever <mc...@apache.org>
escreveu:
> > We cut 4.0 in May and released it in July. It is difficult to plan for a
> release date so we should probably agree on the cut date. One year after
> 4.0 that would make us cut the new branch in May.
>
>
> This makes sense to me. The time between each rc1 cut is the only
> thing we control. We want the rc1 cut to GA published time frame to be
> minimised (that is the goal of stable-trunk) but that it is a
> variable, and not something we want to put pressure on or compromise.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [DISCUSS] Next release cut
Posted by Mick Semb Wever <mc...@apache.org>.
> We cut 4.0 in May and released it in July. It is difficult to plan for a
release date so we should probably agree on the cut date. One year after
4.0 that would make us cut the new branch in May.
This makes sense to me. The time between each rc1 cut is the only
thing we control. We want the rc1 cut to GA published time frame to be
minimised (that is the goal of stable-trunk) but that it is a
variable, and not something we want to put pressure on or compromise.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org