[ https://issues.redhat.com/browse/ISPN-11691?page=com.atlassian.jira.plugi... ] Ryan Emerson commented on ISPN-11691: ------------------------------------- [~dan.berindei] When this workflow was [proposed|https://infinispan.zulipchat.com/#narrow/stream/121836-internal/...] I don't think it was intended to catch all of the already deprecated features, rather it should be adopted for all deprecations/removals moving forward. As our discussion started on an open PR, this workflow is valid for that deprecation and removal. For items that have already been deprecated without a removal Jira, we can use your git command to detect that code should be removed. However when it comes to remove the code, a sub-task on the major version's removal Jira should be created, or at the very least a link added to the Jira associated with the PR removing the code. This way we have a single source of information about all removals in a given major version. -- This message was sent by Atlassian Jira (v7.13.8#713008)