> Please no TCM/accord. That is why everyone will be on 5.0/5.1 for years. I'll > be the person to say it outloud. I'm happy to be proven wrong but let's be > realistic.
Could you elaborate why a stable feature (TCM) is mentioned here alongside with a feature under development? Why specifically do you think TCM will keep everyone on 5.0/5.1? The only concern I _ever_ heard voiced about TCM is that there's no downgrade path after you are already on TCM, but you _can_ downgrade to the previous major version without any problem (see [1], which includes CCM test script which shows the downgrade path working), even after doing schema changes & a host replacement _after_ initializing the CMS. > I'll be the person to say it outloud Could you elaborate on what concerns you've heard? Do you mean there's wider unspoken concern in the community about upgrading to TCM? I'm curious if there's feedback I've missed. Thanks --Alex [1] https://issues.apache.org/jira/browse/CASSANDRA-20145 On Sun, Oct 12, 2025, at 5:28 PM, Chris Lohfink wrote: >> But it should include all features from trunk that we consider to be >> production ready (that includes TCM in my book) > > Please no TCM/accord. That is why everyone will be on 5.0/5.1 for years. I'll > be the person to say it outloud. I'm happy to be proven wrong but let's be > realistic. > > Chris
