jolshan commented on code in PR #16841:
URL: https://github.com/apache/kafka/pull/16841#discussion_r1715593171
##########
server-common/src/main/java/org/apache/kafka/server/common/MetadataVersion.java:
##########
@@ -244,7 +244,7 @@ public enum MetadataVersion {
* <strong>Think carefully before you update this value. ONCE A METADATA
VERSION IS PRODUCTION,
* IT CANNOT BE CHANGED.</strong>
*/
- public static final MetadataVersion LATEST_PRODUCTION = IBP_3_8_IV0;
+ public static final MetadataVersion LATEST_PRODUCTION = IBP_3_9_IV0;
Review Comment:
I don't think MV needs to tie to unstable versions. We used to not have
unstable metadata versions in a release, but now we allow it if the MV is for
the next release and we have the mechanisms to do this.
I think generally, the unstable api version in a release is OK, BUT if we
say the KIP is completed in the release, the api should be stable (unless we
doing using early access etc). I don't think we need to tie api versions to MV
at this time.
--
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]
