Skip to content

Fix the since value of the Pacemaker deprecations: 3.2.0, not 3.1.0 - #9274

Merged
reiabreu merged 1 commit into
apache:masterfrom
reiabreu:fix-pacemaker-deprecated-since
Nov 11, 2026
Merged

reiabreu merged 1 commit into
apache:masterfrom
reiabreu:fix-pacemaker-deprecated-since

Conversation

@reiabreu

Copy link
Copy Markdown
Contributor

The Pacemaker classes, Config and DaemonConfig constants are marked @Deprecated(since = "3.1.0", forRemoval = true), but they were first deprecated after 3.1.0 was released:

This changes since = "3.1.0" to since = "3.2.0" on those 21 annotations (16 files). Nothing else is touched.

  • Checked: the 21 are all the since = "3.1.0" annotations in the repository, and none of the 21 targets has a @Deprecated at v3.1.0. No other text mentions 3.1.0 for these. storm-client and storm-server build, with no checkstyle warning on the changed lines.
  • Not changed: the 3.2.0 release notes and the upgrade note of Formally mark Pacemaker subsystem and configs for removal (#8994) #9171 still quote since = "3.1.0". They are already published, so this fix only reaches the code.

Follow-up to #8994.

🤖 Generated with Claude Code

Pacemaker was first marked @deprecated in apache#9084, after 3.1.0 had been released,
so the 21 annotations from apache#9084 and apache#9171 should say since = "3.2.0".

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@reiabreu
reiabreu merged commit 8a16ae8 into apache:master Nov 11, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant