[
https://issues.apache.org/jira/browse/CASSANDRA-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774347#comment-17774347
]
Stefan Miklosovic edited comment on CASSANDRA-18912 at 10/12/23 7:05 AM:
-------------------------------------------------------------------------
[~mck] I think we are done here. We intentionally left out forRemoval in
Deprecated method, that is quite tricky to get right and we have at least
something to deliver quickly for initial mapping what technical debt we have ...
I plan to deliver some detailed statistics per version etc. in follow-up work
and we decide what to do with it.
was (Author: smiklosovic):
[~mck] I think we are done here. We intentionally left out forRemoval in
Deprecated method, that is quite tricky to get right and we have at least
something to deliver quick for initial mapping what technical debt we have ...
I plan to deliver some detail statistics per version etc in follow up work and
we decide what to do with it.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
