Skip to content

MINOR: Bump LATEST_PRODUCTION to 4.4-IV2 for 4.4.0 - #23235

Open
kaijaytu wants to merge 1 commit into
apache:4.4from
kaijaytu:bump-latest-production-4.4-IV2
Open

MINOR: Bump LATEST_PRODUCTION to 4.4-IV2 for 4.4.0#23235
kaijaytu wants to merge 1 commit into
apache:4.4from
kaijaytu:bump-latest-production-4.4-IV2

Conversation

@kaijaytu

@kaijaytu kaijaytu commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Reported on the 4.4.0 RC0 vote thread: metadata.version in RC0 shipped as 4.3-IV0 instead of 4.4-IV2.

KIP-1191 (IBP_4_4_IV0), KIP-1276 (IBP_4_4_IV1), and KIP-1312 (IBP_4_4_IV2) have all been merged for the 4.4 release. Bump LATEST_PRODUCTION to IBP_4_4_IV2 so these features are actually enabled in 4.4.0.

Also move the "unstable versions" comment block after IBP_4_4_IV2 per the in-file instruction, update LATEST_STABLE_METADATA_VERSION in tests/kafkatest/version.py to match, and adjust MetadataVersionTest and FormatterTest so the "unstable latest" invariants are asserted conditionally (matching the pattern established on trunk in #23125), since on the 4.4 release branch there is no unstable MetadataVersion after the promoted one.

Testing

Ran ./gradlew build locally on JDK 17, plus targeted:

  • ./gradlew server-common:test --tests "*MetadataVersion*"
  • ./gradlew metadata:test --tests "*FormatterTest*"
  • ./gradlew tools:test --tests "*FeatureCommandTest*"

All green.

Reported-by: Andrew Schofield on the 4.4.0 RC0 vote thread
Reviewers: Chia-Ping Tsai chia7712@gmail.com

KIP-1191 (IBP_4_4_IV0), KIP-1276 (IBP_4_4_IV1), and KIP-1312 (IBP_4_4_IV2) have all been merged for the 4.4 release. Bump LATEST_PRODUCTION to IBP_4_4_IV2 so these features are actually enabled in 4.4.0.

Also move the "unstable versions" comment block after IBP_4_4_IV2 per the in-file instruction, update LATEST_STABLE_METADATA_VERSION in tests/kafkatest/version.py to match, and adjust MetadataVersionTest and FormatterTest so the "unstable latest" invariants are asserted conditionally (matching the pattern established on trunk in apache#23125), since on the 4.4 release branch there is no unstable MetadataVersion after the promoted one.

Reported-by: Andrew Schofield on the 4.4.0 RC0 vote thread
Co-Authored-By: Claude Opus 4.7 <claude@anthropic.com>
@kaijaytu

Copy link
Copy Markdown
Contributor Author

cc @chia7712 as 4.4.0 release manager, and @AndrewJSchofield who reported this on the RC0 vote thread. Requesting review so this can go into 4.4.0 RC1.

LATEST_STABLE_TRANSACTION_VERSION = 2
# This should match the LATEST_PRODUCTION version defined in MetadataVersion.java
LATEST_STABLE_METADATA_VERSION = "4.3-IV0"
LATEST_STABLE_METADATA_VERSION = "4.4-IV2"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you please run the related E2E test locally?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on the way!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants