Re: [DISCUSS] putting versions into Deprecated annotations

To me this seems insufficient. As a developer, I'd like to see what the alternative is when reading the javadoc without having to go to Jira. What I would prefer is to know what the alternative is and how to use it. For example: /** @deprecated Use {@link #alternative} instead. See

Re: [DISCUSS] putting versions into Deprecated annotations

Hello everyone, I've discussed with Stefan some steps we can take to improve the final solution, so the final version might look like this: /** @deprecated See CASSANDRA-6504 */ @Deprecated(since = "2.1") public Integer concurrent_replicates = null; The issue number will be taken from the git

Re: Need Confluent "Create" permission for filing a CEP

Thank you! On Tue, Oct 10, 2023 at 2:58 AM Brandon Williams wrote: > I've added you, you should have access now. > > Kind Regards, > Brandon > > On Tue, Oct 10, 2023 at 1:24 AM Jaydeep Chovatia > wrote: > > > > Hi, > > > > I want to create a new CEP request but do not see the "Create" page >

Re: Avoiding pushes to broken branches

What about having a nag-bot that notifies #cassandra-dev on ASF slack hourly if the builds are broken? On Tue, Oct 10, 2023, at 8:02 AM, Mick Semb Wever wrote: > I'd like to suggest some improvements for identifying and announcing > broken branches and to avoid pushing commits to broken

Re: [DISCUSS] putting versions into Deprecated annotations

Sounds like we're relitigating the basics of how @Deprecated, forRemoval, since, and javadoc @link all intersect to make deprecation less painful ;) So: 1. Built-in java.lang.Deprecated: required 2. Can use since and forRemoval if you have that info handy and think it'd be useful (would make

Avoiding pushes to broken branches

I'd like to suggest some improvements for identifying and announcing broken branches and to avoid pushing commits to broken branches. For CI we should have two gates. The first is pre-commit testing, which we have already discussed, e.g. either ci-cassandra or circleci can be used (and repeated

Re: Need Confluent "Create" permission for filing a CEP

I've added you, you should have access now. Kind Regards, Brandon On Tue, Oct 10, 2023 at 1:24 AM Jaydeep Chovatia wrote: > > Hi, > > I want to create a new CEP request but do not see the "Create" page > permission on Confluent. Could someone permit me? > Here is the CEP draft: [DRAFT] CEP -

Re: [DISCUSS] putting versions into Deprecated annotations

OK. Let's go with in-built java.lang.Deprecated annotation. If somebody wants to document that in more detail, there are Javadocs as mentioned. Let's just stick with the standard stuff. I will try to implement this for 5.0 (versions since it was deprecated) with my take on what should be

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

I have been exploring adding a second Path to the Cassandra File object. The original path being the path within the standard Cassandra directory tree and the second being a translated path when there is what was called a ChannelProxy in place. A problem arises when the

[RESULT][VOTE] Accept java-driver

> > The vote will be open for 72 hours (or longer). Votes by PMC members are > considered binding. A vote passes if there are at least three binding +1s and > no -1's. Vote passes with 30 +1s (ten binding). This page is updated:

Need Confluent "Create" permission for filing a CEP

Hi, I want to create a new CEP request but do not see the "Create" page permission on Confluent . Could someone permit me? Here is the CEP draft: [DRAFT] CEP - Apache Cassandra Official Repair Solution - Google Docs