Code freeze starts 1st May. Anything to be addressed?

[Ekaterina Dimitrova]

Hi everyone,

Kind reminder that 1st May is around the corner. What does this mean? Our
code freeze starts on 1st May and my understanding is that only bug fixing
can go into the 4.1 branch.
If anyone has anything to raise, now is a good time. On my end I saw a few
things for this week that we should probably put to completion:
- CASSANDRA-17571  -
I have to close this one, it is in progress; new types in Config is good to
be in before the freeze I guess, even if It is not yaml change
- CASSANDRA-17557  -
we need to take care of the parameters so we don't have to deprecate and
 support anything not actually needed; I think it is probably more or less
done
- CASSANDRA-17379  -
adds a new flag around config; I think it is more or less done, depends on
final CI and second reviewer maybe needed?
- JMX intercept Cassandra exceptions, I think David mentioned a rebase was
needed
- CASSANDRA-17212 - The config property minimum_keyspace_rf and their
nodetool getter and setter commands are new to 4.1. They are suitable to be
ported to guardrails, and if we do this port in 4.1 we won't need to
deprecate that property and nodetool commands in the next release, just one
release after their introduction.

I guess the failing tests we see could be fixed after the freeze but no API
changes.

Thanks everyone for all the hard work. Please don’t hesitate to raise the
flag with questions, concerns or any help needed.

Best regards,
Ekaterina

Re: Code freeze starts 1st May. Anything to be addressed?

[Paulo Motta]

Hi Ekaterina,

Thanks for bringing this up.

I'm hoping to complete the following tickets before the freeze before May
1st:

-  List snapshots of
dropped tables
which will unblock:
-  Add
auto_snapshot_ttl configuration

In addition to the following from Stefan which I'm involved as reviewer:
-  Implement startup
check to prevent Cassandra start to spread zombie data

Cheers,

Paulo

Em seg., 25 de abr. de 2022 às 12:18, Ekaterina Dimitrova <
e.dimitr...@gmail.com> escreveu:

> Hi everyone,
>
> Kind reminder that 1st May is around the corner. What does this mean? Our
> code freeze starts on 1st May and my understanding is that only bug fixing
> can go into the 4.1 branch.
> If anyone has anything to raise, now is a good time. On my end I saw a few
> things for this week that we should probably put to completion:
> - CASSANDRA-17571  -
> I have to close this one, it is in progress; new types in Config is good to
> be in before the freeze I guess, even if It is not yaml change
> - CASSANDRA-17557  -
> we need to take care of the parameters so we don't have to deprecate and
>  support anything not actually needed; I think it is probably more or less
> done
> - CASSANDRA-17379  -
> adds a new flag around config; I think it is more or less done, depends on
> final CI and second reviewer maybe needed?
> - JMX intercept Cassandra exceptions, I think David mentioned a rebase was
> needed
> - CASSANDRA-17212 - The config property minimum_keyspace_rf and their
> nodetool getter and setter commands are new to 4.1. They are suitable to be
> ported to guardrails, and if we do this port in 4.1 we won't need to
> deprecate that property and nodetool commands in the next release, just one
> release after their introduction.
>
> I guess the failing tests we see could be fixed after the freeze but no
> API changes.
>
> Thanks everyone for all the hard work. Please don’t hesitate to raise the
> flag with questions, concerns or any help needed.
>
> Best regards,
> Ekaterina
>

[FOR REVIEW] Liquibase case study blog post

[Chris Thornett]

To highlight the recent Liquibase case study, we're posting a short blog:
https://docs.google.com/document/d/1LAI3Rd_95a2WQ06-yv2v8FQoLoCmZLGnHhHN7X4nM2w/edit?usp=sharing


For those interested, this is open for comments with the usual 72-hour
review window. The aim is to publish this on Thursday (28th April).

Thanks,
-- 

Chris Thornett
senior content strategist, Constantia.io
ch...@constantia.io