We know we are turning away more and more contributions and new potential
> dev community with our 4.0 feature freeze, and it has been going on for a
> while now.
>
> I would like to suggest we create a cassandra-5.0 branch where we can
> start to queue up all reviewed and ready-to-go post-4.0 comm
On Tue, Sep 15, 2020 at 4:00 PM Mick Semb Wever wrote:
> So far no one has indicated any desire to maintain a cassandra-5.0 branch.
Sorry, I'm just catching up from vacation. I'd be glad to help with this.
-
To unsubscribe, e-m
> But I would suggest that we are more productive when
> raising and discussing concrete examples and specific patches
You make a good point. Can you provide some concrete examples of your own?
Ironically, this entire proposal so far rests on hypothetical lost
contributions by hypothetical comp
