I have worked with teams that have lost weeks of sleep, and customers, due to these issues. It cost a fortune 500 company that I work with millions in revenue. I think ignorance is bliss may also apply to us, if we are unaware of the number of times C* users have been bit by this issue but not raised a big stink on the ML.
I lean towards applying the patch to all branches. Jon On Thu, Sep 12, 2024 at 11:07 AM Brandon Williams <dri...@gmail.com> wrote: > On Thu, Sep 12, 2024 at 11:52 AM Josh McKenzie <jmcken...@fastmail.com> > wrote: > > > > More or less surprising than learning that they've been at risk of or > actively losing data for years? > > Ignorance is bliss though and I think the majority of users haven't > lost sleep over this since it's been present since the beginning of > time. Changing behavior in old stable branches can interrupt that, > especially if a regression is introduced, which is always a > possibility. Logging will provide awareness and I think that's going > far enough on our side, and users who are concerned can go further on > theirs. > > Kind Regards, > Brandon >
