reiabreu commented on issue #8994:
URL: https://github.com/apache/storm/issues/8994#issuecomment-6782458247
*Generated with the help of an LLM.*
**Status after #9266: the annotation cleanup is done. The removals are what
is missing.**
**Done** (checked on `master` at `321595f`)
- Inventory and classification: #9172, #9173, #9266. All 103 production
`@Deprecated` annotations have `since` and an explicit `forRemoval` (89 `true`,
14 `false`).
- Removals whose window had passed: #9167–#9170.
- Pacemaker marked `forRemoval`: #9171.
**Missing**
1. **Remove the 89 APIs marked `forRemoval = true`.** By module:
`storm-client` 54, `storm-server` 19, `external/storm-hdfs` 12,
`flux/flux-core` 4. 37 are from 2.0.0 and 15 from 2.6.4.
- Removals ship in 3.x releases, not only in a major version. This
replaces the guideline in the issue description. Each breaking change goes in
the PR description under `## Upgrade notes`, so it reaches the release notes.
- One PR per module or coherent group, each with its tests, docs, and
`defaults.yaml` and validation entries.
- Nothing is filed yet. The sub-tasks in the description are still
unchecked.
2. **Decide on the OpenRewrite "Find Deprecated Uses" action** suggested on
2026-10-18. No PR has come out of it. It is useful for finding internal callers
before a removal.
**Not needed:** a `docs/` page listing deprecated or removed APIs. The
release notes cover it.
This issue stays open until the removals are done or moved to their own
issues.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]