[ https://issues.apache.org/jira/browse/CASSANDRA-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Miklosovic updated CASSANDRA-18912: ------------------------------------------ Reviewers: Brandon Williams, Maxim Muzafarov Status: Review In Progress (was: Needs Committer) > Specify "since" in all Deprecated annotations > --------------------------------------------- > > Key: CASSANDRA-18912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18912 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Core > Reporter: Stefan Miklosovic > Assignee: Maxim Muzafarov > Priority: Normal > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > It would be great if we introduced in 5.0 a change in Deprecated annotations > like this: > {code} > @Deprecated(since = "4.0") > {code} > or > {code} > @Deprecated(since = "3.11") > {code} > The reasoning behind this is that as of now, it is pretty cumbersome to > figure out what can be removed on the next major version. It has to be, > basically, done manually every time. > There is also this parameter available: > {code} > @Deprecated(forRemoval = true / false) > {code} > which indicates whether the annotated element is subject to removal in a > future version so we do not need to think about this every time if it is > eligible for deletion in a next major or not. > We could then have a check which would ensure that we are not releasing a > next major with some deprecations introduced two majors before. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org