> Yes. Any reason to have releases for users outside of Cassandra ? And is > there any cross-branch/version interaction, like there is with the > jvm-dtest-api ?
As of today, Harry tries not to rely on branch versions. Harry-core is completely free of Cassandra dependency (for which I had to copy some concurrency primitives, but they will go away if we bring it in-tree). You will still be able to write upgrade tests more or less how you write upgrade tests today: with API that is limited to cross-version jvm-dtest-api. > (We can publish jar files at C* release time if there's a call for this, > doesn't really matter if they don't contain changes.). I would say we should publish dtest jar files when releasing, this would be very helpful! On Fri, Nov 24, 2023, at 5:23 PM, Mick Semb Wever wrote: > > > >> I had conversations with several folks, and wanted to propose to move >> harry-core to Cassandra test tree. This will substantially >> simplify/streamline co-development of Cassandra and Harry. With a new >> HistoryBuilder API that has helped to find and trigger [1] [2] and [3], it >> will also be much more approachable. > > > Yes. Any reason to have releases for users outside of Cassandra ? (We can > publish jar files at C* release time if there's a call for this, doesn't > really matter if they don't contain changes.). And is there any > cross-branch/version interaction, like there is with the jvm-dtest-api ? > > >
