The patches for this issue have gotten a +1 from Mick, and that meets our strict 2 committer rule, but I'm posting them here in case anyone else wants take a look:
4.0: https://github.com/apache/cassandra/pull/3526 4.1: https://github.com/apache/cassandra/pull/3539 5.0: https://github.com/apache/cassandra/pull/3544 On Sun, Sep 15, 2024 at 10:21 AM Brandon Williams <dri...@gmail.com> wrote: > +1 for declaring things like this in the vote/release emails. > > Kind Regards, > Brandon > > On Sun, Sep 15, 2024 at 10:17 AM Michael Shuler <mich...@pbandjelly.org> > wrote: > > > > I've stated this same opinion prior, fix was in NEWS.txt and users had a > > bad day with a behavior change. Perhaps this kind of inclusion needs > > more exposure. This is exactly the sort of change may *also* be best > > stated clearly in the vote/release emails, ala: > > > > <release bits> > > ================================================== > > This release contains a relatively major change you should be aware of, > > with xyz fix, new default, and with the behavior change, here are the > > new defaults, how to disable, etc... > > ================================================== > > kthxbai. > > > > Just do everything possible to convey what operators need to know, > > wherever we can, if we include the fix. Link to NEWS.txt is insufficient > > in this sort of case. > > > > Warm regards, > > Michael > > > > On 9/12/24 13:16, Abe Ratnofsky wrote: > > > Expressing another vote in favor of rejection-by-default. If a user > doesn't want to lose sleep for data loss while on-call, they can read > NEWS.txt and disable rejection. > > > >
