[
https://issues.apache.org/jira/browse/CASSANDRA-18938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18938:
------------------------------------------
Change Category: Code Clarity
Complexity: Normal
Fix Version/s: 5.x
Status: Open (was: Triage Needed)
> Map and possibly remove Deprecated code
> ---------------------------------------
>
> Key: CASSANDRA-18938
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18938
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
>
> This is follow-up of CASSANDRA-18912. We should scan the project and document
> what was deprecated and when (based on "since" added to Deprecated
> annotation).
> Once this is done, we need to identify what should be removed and what should
> stay.
> It is questionable if this ticket will result in some actual code change. I
> think we should firstly just map what was deprecated to have a bigger picture
> where we are. Then we can discuss what to actually remove.
--
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
