Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Josh McKenzie]

Merge path for bugs on 3.0 is pretty brutal at this point. Good thing 2 will 
drop off when we GA 5.0.

Updated wiki w/new branches plus some examples: link 


On Mon, Aug 7, 2023, at 11:18 AM, Mick Semb Wever wrote:
> 
> Forward merging cassandra-4.1 … cassandra-5.0 … trunk is now required ! 
> 
> trunk is still got 5.0 in the build.xml, but that's only temporary until 
> 18705 lands, and of no harm i believe… (i could easily be wrong, but not 
> AFAIK)
> 
> 
> On Mon, 7 Aug 2023 at 13:38, Brandon Williams  wrote:
>> Is this intended to be used now and change the merge order?  I ask
>> because 18705 mentions bumping build.xml and CHANGES.txt amongst
>> others that haven't been done which is leading to confusion.
>> 
>> Kind Regards,
>> Brandon
>> 
>> On Sat, Aug 5, 2023 at 4:46 PM Mick Semb Wever  wrote:
>> >
>> >
>> > With no objections, and everything folk mentioned above in, the 
>> > cassandra-5.0 branch is cut.
>> >
>> > Next steps are bumping trunk to 5.1 and then cutting a 5.0-alpha1
>> >
>> > The bumping to 5.1 has a few steps involved in it, but the initial in-tree 
>> > PRs are ready for review, with CI being run, see CASSANDRA-18705
>> >
>> >
>> >
>> > On Sat, 29 Jul 2023 at 00:00, Brandon Williams  wrote:
>> >>
>> >> +1 to everything stated here.
>> >>
>> >> Kind Regards,
>> >> Brandon
>> >>
>> >> On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever  wrote:
>> >> >
>> >> >
>> >> > The previous thread¹ on when to freeze 5.0 landed on freezing the first 
>> >> > week of August, with a waiver in place for TCM and Accord to land later 
>> >> > (but before October).
>> >> >
>> >> > With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 
>> >> > work that hasn't landed is Vector search (CEP-30).
>> >> >
>> >> > Are there any objections to a waiver on Vector search?  All the 
>> >> > groundwork: SAI and the vector type; has been merged, with all 
>> >> > remaining work expected to land in August.
>> >> >
>> >> > I'm keen to freeze and see us shift gears – there's already SO MUCH in 
>> >> > 5.0 and a long list of flakies.  It takes time and patience to triage 
>> >> > and identify the bugs that hit us before GA.  The freeze is about being 
>> >> > "mostly feature complete",  so we have room for things before our first 
>> >> > beta (precedence is to ask).   If we hope for a GA by December, account 
>> >> > for the 6 weeks turnaround time for cutting and voting on one alpha, 
>> >> > one beta, and one rc release, and the quiet period that August is, we 
>> >> > really only have September and October left.
>> >> >
>> >> > I already feel this is asking a bit of a miracle from us given how 4.1 
>> >> > went (and I'm hoping I will be proven wrong).
>> >> >
>> >> > In addition, are there any objections to cutting an 5.0-alpha1 release 
>> >> > as soon as we freeze?
>> >> >
>> >> > This is on the understanding vector, tcm and accord will become 
>> >> > available in later alphas.  Originally the discussion¹ was waiting for 
>> >> > Accord for alpha1, but a number of folk off-list have requested earlier 
>> >> > alphas to help with testing.
>> >> >
>> >> >
>> >> > ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Mick Semb Wever]

Forward merging cassandra-4.1 … cassandra-5.0 … trunk is now required !

trunk is still got 5.0 in the build.xml, but that's only temporary until
18705 lands, and of no harm i believe… (i could easily be wrong, but not
AFAIK)


On Mon, 7 Aug 2023 at 13:38, Brandon Williams  wrote:

> Is this intended to be used now and change the merge order?  I ask
> because 18705 mentions bumping build.xml and CHANGES.txt amongst
> others that haven't been done which is leading to confusion.
>
> Kind Regards,
> Brandon
>
> On Sat, Aug 5, 2023 at 4:46 PM Mick Semb Wever  wrote:
> >
> >
> > With no objections, and everything folk mentioned above in, the
> cassandra-5.0 branch is cut.
> >
> > Next steps are bumping trunk to 5.1 and then cutting a 5.0-alpha1
> >
> > The bumping to 5.1 has a few steps involved in it, but the initial
> in-tree PRs are ready for review, with CI being run, see CASSANDRA-18705
> >
> >
> >
> > On Sat, 29 Jul 2023 at 00:00, Brandon Williams  wrote:
> >>
> >> +1 to everything stated here.
> >>
> >> Kind Regards,
> >> Brandon
> >>
> >> On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever  wrote:
> >> >
> >> >
> >> > The previous thread¹ on when to freeze 5.0 landed on freezing the
> first week of August, with a waiver in place for TCM and Accord to land
> later (but before October).
> >> >
> >> > With JDK8 now dropped and SAI and UCS merged, the only expected 5.0
> work that hasn't landed is Vector search (CEP-30).
> >> >
> >> > Are there any objections to a waiver on Vector search?  All the
> groundwork: SAI and the vector type; has been merged, with all remaining
> work expected to land in August.
> >> >
> >> > I'm keen to freeze and see us shift gears – there's already SO MUCH
> in 5.0 and a long list of flakies.  It takes time and patience to triage
> and identify the bugs that hit us before GA.  The freeze is about being
> "mostly feature complete",  so we have room for things before our first
> beta (precedence is to ask).   If we hope for a GA by December, account for
> the 6 weeks turnaround time for cutting and voting on one alpha, one beta,
> and one rc release, and the quiet period that August is, we really only
> have September and October left.
> >> >
> >> > I already feel this is asking a bit of a miracle from us given how
> 4.1 went (and I'm hoping I will be proven wrong).
> >> >
> >> > In addition, are there any objections to cutting an 5.0-alpha1
> release as soon as we freeze?
> >> >
> >> > This is on the understanding vector, tcm and accord will become
> available in later alphas.  Originally the discussion¹ was waiting for
> Accord for alpha1, but a number of folk off-list have requested earlier
> alphas to help with testing.
> >> >
> >> >
> >> > ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3
>

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Brandon Williams]

Is this intended to be used now and change the merge order?  I ask
because 18705 mentions bumping build.xml and CHANGES.txt amongst
others that haven't been done which is leading to confusion.

Kind Regards,
Brandon

On Sat, Aug 5, 2023 at 4:46 PM Mick Semb Wever  wrote:
>
>
> With no objections, and everything folk mentioned above in, the cassandra-5.0 
> branch is cut.
>
> Next steps are bumping trunk to 5.1 and then cutting a 5.0-alpha1
>
> The bumping to 5.1 has a few steps involved in it, but the initial in-tree 
> PRs are ready for review, with CI being run, see CASSANDRA-18705
>
>
>
> On Sat, 29 Jul 2023 at 00:00, Brandon Williams  wrote:
>>
>> +1 to everything stated here.
>>
>> Kind Regards,
>> Brandon
>>
>> On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever  wrote:
>> >
>> >
>> > The previous thread¹ on when to freeze 5.0 landed on freezing the first 
>> > week of August, with a waiver in place for TCM and Accord to land later 
>> > (but before October).
>> >
>> > With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work 
>> > that hasn't landed is Vector search (CEP-30).
>> >
>> > Are there any objections to a waiver on Vector search?  All the 
>> > groundwork: SAI and the vector type; has been merged, with all remaining 
>> > work expected to land in August.
>> >
>> > I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 
>> > and a long list of flakies.  It takes time and patience to triage and 
>> > identify the bugs that hit us before GA.  The freeze is about being 
>> > "mostly feature complete",  so we have room for things before our first 
>> > beta (precedence is to ask).   If we hope for a GA by December, account 
>> > for the 6 weeks turnaround time for cutting and voting on one alpha, one 
>> > beta, and one rc release, and the quiet period that August is, we really 
>> > only have September and October left.
>> >
>> > I already feel this is asking a bit of a miracle from us given how 4.1 
>> > went (and I'm hoping I will be proven wrong).
>> >
>> > In addition, are there any objections to cutting an 5.0-alpha1 release as 
>> > soon as we freeze?
>> >
>> > This is on the understanding vector, tcm and accord will become available 
>> > in later alphas.  Originally the discussion¹ was waiting for Accord for 
>> > alpha1, but a number of folk off-list have requested earlier alphas to 
>> > help with testing.
>> >
>> >
>> > ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Mick Semb Wever]

With no objections, and everything folk mentioned above in, the
cassandra-5.0 branch is cut.

Next steps are bumping trunk to 5.1 and then cutting a 5.0-alpha1

The bumping to 5.1 has a few steps involved in it, but the initial in-tree
PRs are ready for review, with CI being run, see CASSANDRA-18705



On Sat, 29 Jul 2023 at 00:00, Brandon Williams  wrote:

> +1 to everything stated here.
>
> Kind Regards,
> Brandon
>
> On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever  wrote:
> >
> >
> > The previous thread¹ on when to freeze 5.0 landed on freezing the first
> week of August, with a waiver in place for TCM and Accord to land later
> (but before October).
> >
> > With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work
> that hasn't landed is Vector search (CEP-30).
> >
> > Are there any objections to a waiver on Vector search?  All the
> groundwork: SAI and the vector type; has been merged, with all remaining
> work expected to land in August.
> >
> > I'm keen to freeze and see us shift gears – there's already SO MUCH in
> 5.0 and a long list of flakies.  It takes time and patience to triage and
> identify the bugs that hit us before GA.  The freeze is about being "mostly
> feature complete",  so we have room for things before our first beta
> (precedence is to ask).   If we hope for a GA by December, account for the
> 6 weeks turnaround time for cutting and voting on one alpha, one beta, and
> one rc release, and the quiet period that August is, we really only have
> September and October left.
> >
> > I already feel this is asking a bit of a miracle from us given how 4.1
> went (and I'm hoping I will be proven wrong).
> >
> > In addition, are there any objections to cutting an 5.0-alpha1 release
> as soon as we freeze?
> >
> > This is on the understanding vector, tcm and accord will become
> available in later alphas.  Originally the discussion¹ was waiting for
> Accord for alpha1, but a number of folk off-list have requested earlier
> alphas to help with testing.
> >
> >
> > ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3
>

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Brandon Williams]

+1 to everything stated here.

Kind Regards,
Brandon

On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever  wrote:
>
>
> The previous thread¹ on when to freeze 5.0 landed on freezing the first week 
> of August, with a waiver in place for TCM and Accord to land later (but 
> before October).
>
> With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work that 
> hasn't landed is Vector search (CEP-30).
>
> Are there any objections to a waiver on Vector search?  All the groundwork: 
> SAI and the vector type; has been merged, with all remaining work expected to 
> land in August.
>
> I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 
> and a long list of flakies.  It takes time and patience to triage and 
> identify the bugs that hit us before GA.  The freeze is about being "mostly 
> feature complete",  so we have room for things before our first beta 
> (precedence is to ask).   If we hope for a GA by December, account for the 6 
> weeks turnaround time for cutting and voting on one alpha, one beta, and one 
> rc release, and the quiet period that August is, we really only have 
> September and October left.
>
> I already feel this is asking a bit of a miracle from us given how 4.1 went 
> (and I'm hoping I will be proven wrong).
>
> In addition, are there any objections to cutting an 5.0-alpha1 release as 
> soon as we freeze?
>
> This is on the understanding vector, tcm and accord will become available in 
> later alphas.  Originally the discussion¹ was waiting for Accord for alpha1, 
> but a number of folk off-list have requested earlier alphas to help with 
> testing.
>
>
> ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Josh McKenzie]

+1 to what you've stated here Mick with a question: where did we land on 
flagging new features as experimental? Seems like it's an "at author's 
discretion" - search of the list turned up not too much structure there. Had a 
statement to that effect from Benjamin here 
.

I ask because I think there's *a lot* in 5.0 and it's not clear to me that the 
various features have been exercised in comparable ways to gain confidence in 
their prod readiness. For 5.0 we have (or will likely have):
 1. Trie Memtables
 2. Trie Indexed Tables
 3. UCS
 4. SAI
 5. Vector Search
 6. Transactional Metadata
 7. Accord
While 6 (TrM) can't fall under that umbrella for architectural reasons, for the 
rest the label might be useful.

Flip side, of course, is the argument that the features should be exercised 
heavily enough (unit, dtest, harry, simulator, in qa env, etc) before merge 
that nothing merges in that's not prod ready; don't know if that's true or not 
for all the features above (genuinely don't know; not looking to spread FUD), 
and it's not immediately obvious to me that that's the optimal way for us to 
balance innovation vs. stabilization.

Basically I think it'd be nice if "Experimental" fostered more safe innovation 
and expansion in our ecosystem rather than being something of a pariah dumping 
ground to retroactively apply to things that have proven unstable or not 
completed. :) Plus there'd be value in signaling that to users.

Hm. I think that implies feature categories of "alpha (experimental, may be 
removed (see MV's))", "beta (api stable and expected to be prod-hardened)", and 
then prod ready. Bit of a pandora's box now that I type this out; sorry.

On Wed, Jul 26, 2023, at 6:38 PM, J. D. Jordan wrote:
> 
> I think this plan seems reasonable to me. +1
> 
> -Jeremiah
> 
>> On Jul 26, 2023, at 5:28 PM, Mick Semb Wever  wrote:
>> 
>> 
>> The previous thread¹ on when to freeze 5.0 landed on freezing the first week 
>> of August, with a waiver in place for TCM and Accord to land later (but 
>> before October).
>> 
>> With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work 
>> that hasn't landed is Vector search (CEP-30).  
>> 
>> Are there any objections to a waiver on Vector search?  All the groundwork: 
>> SAI and the vector type; has been merged, with all remaining work expected 
>> to land in August.
>> 
>> I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 
>> and a long list of flakies.  It takes time and patience to triage and 
>> identify the bugs that hit us before GA.  The freeze is about being "mostly 
>> feature complete",  so we have room for things before our first beta 
>> (precedence is to ask).   If we hope for a GA by December, account for the 6 
>> weeks turnaround time for cutting and voting on one alpha, one beta, and one 
>> rc release, and the quiet period that August is, we really only have 
>> September and October left.  
>> 
>> I already feel this is asking a bit of a miracle from us given how 4.1 went 
>> (and I'm hoping I will be proven wrong). 
>> 
>> In addition, are there any objections to cutting an 5.0-alpha1 release as 
>> soon as we freeze?  
>> 
>> This is on the understanding vector, tcm and accord will become available in 
>> later alphas.  Originally the discussion¹ was waiting for Accord for alpha1, 
>> but a number of folk off-list have requested earlier alphas to help with 
>> testing.
>> 
>> 
>> ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Ekaterina Dimitrova]

+1 on freeze 1st August with the suggested waiver.

Also, +1 on the idea for alpha 1, as long as we give straight upfront the
right expectations to users.

Now, when we added also JDK17 in CI, I want to encourage people to start
testing it in their test environments and give us some feedback.



On Wed, 26 Jul 2023 at 18:39, J. D. Jordan 
wrote:

> I think this plan seems reasonable to me. +1
>
> -Jeremiah
>
> On Jul 26, 2023, at 5:28 PM, Mick Semb Wever  wrote:
>
> 
>
>
> The previous thread¹ on when to freeze 5.0 landed on freezing the first
> week of August, with a waiver in place for TCM and Accord to land later
> (but before October).
>
> With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work
> that hasn't landed is Vector search (CEP-30).
>
> Are there any objections to a waiver on Vector search?  All the
> groundwork: SAI and the vector type; has been merged, with all remaining
> work expected to land in August.
>
> I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0
> and a long list of flakies.  It takes time and patience to triage and
> identify the bugs that hit us before GA.  The freeze is about being "mostly
> feature complete",  so we have room for things before our first beta
> (precedence is to ask).   If we hope for a GA by December, account for the
> 6 weeks turnaround time for cutting and voting on one alpha, one beta, and
> one rc release, and the quiet period that August is, we really only have
> September and October left.
>
> I already feel this is asking a bit of a miracle from us given how 4.1
> went (and I'm hoping I will be proven wrong).
>
> In addition, are there any objections to cutting an 5.0-alpha1 release as
> soon as we freeze?
>
> This is on the understanding vector, tcm and accord will become available
> in later alphas.  Originally the discussion¹ was waiting for Accord for
> alpha1, but a number of folk off-list have requested earlier alphas to help
> with testing.
>
>
> ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3
>
>

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Miklosovic, Stefan]

I plan to run few builds with Corretto etc and do few manual tests, I will try 
to push that as soon as possible but it might happen it will leak to the next 
week.


From: Mick Semb Wever 
Sent: Thursday, July 27, 2023 0:27
To: dev
Subject: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




The previous thread¹ on when to freeze 5.0 landed on freezing the first week of 
August, with a waiver in place for TCM and Accord to land later (but before 
October).

With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work that 
hasn't landed is Vector search (CEP-30).

Are there any objections to a waiver on Vector search?  All the groundwork: SAI 
and the vector type; has been merged, with all remaining work expected to land 
in August.

I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 and 
a long list of flakies.  It takes time and patience to triage and identify the 
bugs that hit us before GA.  The freeze is about being "mostly feature 
complete",  so we have room for things before our first beta (precedence is to 
ask).   If we hope for a GA by December, account for the 6 weeks turnaround 
time for cutting and voting on one alpha, one beta, and one rc release, and the 
quiet period that August is, we really only have September and October left.

I already feel this is asking a bit of a miracle from us given how 4.1 went 
(and I'm hoping I will be proven wrong).

In addition, are there any objections to cutting an 5.0-alpha1 release as soon 
as we freeze?

This is on the understanding vector, tcm and accord will become available in 
later alphas.  Originally the discussion¹ was waiting for Accord for alpha1, 
but a number of folk off-list have requested earlier alphas to help with 
testing.


¹) 
https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3=05%7C01%7CStefan.Miklosovic%40netapp.com%7C78ec92032b1447066a4d08db8e27993b%7C4b0911a0929b4715944bc03745165b3a%7C0%7C0%7C638260072949964295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=LtsYdfm%2BNOm28l3MuySxG0UQDO%2BesZoCaX%2F7CW0DE6k%3D=0>

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Berenguer Blasi]

SGTM +1

On 27/7/23 6:39, Dinesh Joshi wrote:

Mick,

This sounds like a good plan. CEP-33 and 34 are ready to go. We're 
running into CI related issues but once they clear up we'll merge 
them. I anticipate we'll be done in a week's time.


Thanks,

Dinesh


On Jul 26, 2023, at 3:27 PM, Mick Semb Wever  wrote:


The previous thread¹ on when to freeze 5.0 landed on freezing the 
first week of August, with a waiver in place for TCM and Accord to 
land later (but before October).


With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 
work that hasn't landed is Vector search (CEP-30).


Are there any objections to a waiver on Vector search?  All the 
groundwork: SAI and the vector type; has been merged, with all 
remaining work expected to land in August.


I'm keen to freeze and see us shift gears – there's already SO MUCH 
in 5.0 and a long list of flakies.  It takes time and patience to 
triage and identify the bugs that hit us before GA.  The freeze is 
about being "mostly feature complete",  so we have room for things 
before our first beta (precedence is to ask).   If we hope for a GA 
by December, account for the 6 weeks turnaround time for cutting and 
voting on one alpha, one beta, and one rc release, and the quiet 
period that August is, we really only have September and October left.


I already feel this is asking a bit of a miracle from us given how 
4.1 went (and I'm hoping I will be proven wrong).


In addition, are there any objections to cutting an 5.0-alpha1 
release as soon as we freeze?


This is on the understanding vector, tcm and accord will become 
available in later alphas.  Originally the discussion¹ was waiting 
for Accord for alpha1, but a number of folk off-list have requested 
earlier alphas to help with testing.



¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Dinesh Joshi]

Mick,

This sounds like a good plan. CEP-33 and 34 are ready to go. We're running into 
CI related issues but once they clear up we'll merge them. I anticipate we'll 
be done in a week's time.

Thanks,

Dinesh

> On Jul 26, 2023, at 3:27 PM, Mick Semb Wever  wrote:
> 
> 
> The previous thread¹ on when to freeze 5.0 landed on freezing the first week 
> of August, with a waiver in place for TCM and Accord to land later (but 
> before October).
> 
> With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work that 
> hasn't landed is Vector search (CEP-30).  
> 
> Are there any objections to a waiver on Vector search?  All the groundwork: 
> SAI and the vector type; has been merged, with all remaining work expected to 
> land in August.
> 
> I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 
> and a long list of flakies.  It takes time and patience to triage and 
> identify the bugs that hit us before GA.  The freeze is about being "mostly 
> feature complete",  so we have room for things before our first beta 
> (precedence is to ask).   If we hope for a GA by December, account for the 6 
> weeks turnaround time for cutting and voting on one alpha, one beta, and one 
> rc release, and the quiet period that August is, we really only have 
> September and October left.  
> 
> I already feel this is asking a bit of a miracle from us given how 4.1 went 
> (and I'm hoping I will be proven wrong). 
> 
> In addition, are there any objections to cutting an 5.0-alpha1 release as 
> soon as we freeze?  
> 
> This is on the understanding vector, tcm and accord will become available in 
> later alphas.  Originally the discussion¹ was waiting for Accord for alpha1, 
> but a number of folk off-list have requested earlier alphas to help with 
> testing.
> 
> 
> ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[J. D. Jordan]

I think this plan seems reasonable to me. +1

-Jeremiah

> On Jul 26, 2023, at 5:28 PM, Mick Semb Wever  wrote:
> 
> 
> 
> The previous thread¹ on when to freeze 5.0 landed on freezing the first week 
> of August, with a waiver in place for TCM and Accord to land later (but 
> before October).
> 
> With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work that 
> hasn't landed is Vector search (CEP-30).  
> 
> Are there any objections to a waiver on Vector search?  All the groundwork: 
> SAI and the vector type; has been merged, with all remaining work expected to 
> land in August.
> 
> I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0 
> and a long list of flakies.  It takes time and patience to triage and 
> identify the bugs that hit us before GA.  The freeze is about being "mostly 
> feature complete",  so we have room for things before our first beta 
> (precedence is to ask).   If we hope for a GA by December, account for the 6 
> weeks turnaround time for cutting and voting on one alpha, one beta, and one 
> rc release, and the quiet period that August is, we really only have 
> September and October left.  
> 
> I already feel this is asking a bit of a miracle from us given how 4.1 went 
> (and I'm hoping I will be proven wrong). 
> 
> In addition, are there any objections to cutting an 5.0-alpha1 release as 
> soon as we freeze?  
> 
> This is on the understanding vector, tcm and accord will become available in 
> later alphas.  Originally the discussion¹ was waiting for Accord for alpha1, 
> but a number of folk off-list have requested earlier alphas to help with 
> testing.
> 
> 
> ¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3

August 5.0 Freeze (with waivers…) and a 5.0-alpha1

[Mick Semb Wever]

The previous thread¹ on when to freeze 5.0 landed on freezing the first
week of August, with a waiver in place for TCM and Accord to land later
(but before October).

With JDK8 now dropped and SAI and UCS merged, the only expected 5.0 work
that hasn't landed is Vector search (CEP-30).

Are there any objections to a waiver on Vector search?  All the groundwork:
SAI and the vector type; has been merged, with all remaining work expected
to land in August.

I'm keen to freeze and see us shift gears – there's already SO MUCH in 5.0
and a long list of flakies.  It takes time and patience to triage and
identify the bugs that hit us before GA.  The freeze is about being "mostly
feature complete",  so we have room for things before our first beta
(precedence is to ask).   If we hope for a GA by December, account for the
6 weeks turnaround time for cutting and voting on one alpha, one beta, and
one rc release, and the quiet period that August is, we really only have
September and October left.

I already feel this is asking a bit of a miracle from us given how 4.1 went
(and I'm hoping I will be proven wrong).

In addition, are there any objections to cutting an 5.0-alpha1 release as
soon as we freeze?

This is on the understanding vector, tcm and accord will become available
in later alphas.  Originally the discussion¹ was waiting for Accord for
alpha1, but a number of folk off-list have requested earlier alphas to help
with testing.


¹) https://lists.apache.org/thread/9c5cnn57c7oqw8wzo3zs0dkrm4f17lm3