> I think it is good to document further things and keep on doing it in time
> when discussions happen. I can see this being a benefit both for users and
> Cassandra developers.
Strong +1 from me here. Having guidance for people working on the codebase to
understand what is and isn't considered
Slower past couple of weeks; a lot of focus on burning down failing tests.
We're at 5 weeks without a build lead (details on the role here:
https://cwiki.apache.org/confluence/display/CASSANDRA/Build+Lead). I've taken
on the role a few times myself this year already and it's really helpful to ge
I don’t think it has to be all that complicated?
If it’s a part of our UX it’s probably something we should maintain backwards
compatibility for.
If it’s part of our internal codebase, probably not. The only two “public” APIs
we have inside the codebase that I’m aware of are triggers and second
