Strong +1 on prioritizing community engagement 1st and caution second, though still prioritizing it. I think the right metric for us to calibrate around is that "disrupt in-flight testing cycles", i.e. if changes cause significant rework for people that have already begun testing 4.0, probably ok to review and get it in but target 4.0.x.
On Thu, Nov 22, 2018 at 12:00 PM Benedict Elliott Smith <bened...@apache.org> wrote: > > I assume it's obvious to everyone that this should be taken on a > > case-by-case basis. There's at least 2 that were in that list (one of > which > > Marcus bumped off PA) that are potentially big and hairy changes that > would > > disrupt in-flight testing cycles. > > Agreed. I’d prefer we aim to be as permissive as practical, though. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
