adoroszlai commented on PR #11930: URL: https://github.com/apache/ozone/pull/11930#issuecomment-6651815973
> Compatibility: the version has not been in any release yet (not in 2.1.x or 2.2.x), so now is the time to rename it. The serialized value stays 101, so the wire format is unchanged. Only the Java constant name changes. I think the java constant can be renamed anytime, does not affect compatibility. > But how about the practice of HDDSVersion on DN side? Can we also have the version number starting from day 0 or we should only add a version number after the feature is complete on DN? Please see the [developer guide about upgrade compatibility](https://ozone.apache.org/docs/next/developer-guide/develop/upgrade-compatibility#committing-changes). -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
