A good time for NGCC will be closer to 4.0 release where we can plan what
we can put it on 4.0-next. I am not sure doing it now is going to help when
we are months away from 4.0 release.
On Fri, Aug 31, 2018 at 7:42 AM Jay Zhuang wrote:
> Are we going to have a dev event next month? Or anything
I'm thinking a month or two after 4.0 would give us time to unwind after
the release and start to give real thought to big changes coming in the
next release. Let's focus on one thing at a time.
On Wed, Sep 5, 2018 at 12:29 PM sankalp kohli
wrote:
> A good time for NGCC will be closer to 4.0 re
+1 to Jon's sentiment. Further, perhaps we should use that time after
GA'ing 4.0 to poll our users what they need/want from the next major
release of the database.
On Wed, Sep 5, 2018 at 9:31 AM, Jonathan Haddad wrote:
> I'm thinking a month or two after 4.0 would give us time to unwind after
>
Another thing to discuss will be how to improve testing further from the
learning of finding bugs in C* 4.0.
On Wed, Sep 5, 2018 at 9:57 AM Jason Brown wrote:
> +1 to Jon's sentiment. Further, perhaps we should use that time after
> GA'ing 4.0 to poll our users what they need/want from the next
> How would we be sure users will never encounter bugs unless we build
> against that JDK?
Apache Cassandra does not distribute JDK1.7 built releases.
The only way a user could repeat such a bug is if they have built C* themselves.
I don't think the project should be responsible for every p
