errose28 commented on PR #6916: URL: https://github.com/apache/ozone/pull/6916#issuecomment-2297500279
> do you think we should also have this run for 1.4.0 branch or run for older release branches as well? This would be applicable where we might backport changes? Or is it expected that config related changes will only be present on the latest release at the time and older releases will only receive fixes? This is a good question. I think defining a mapping between release branches and locations in the docs may be difficult to maintain. This is true whether the docs live in the ozone or ozone-site repo, since doc versions are stored in different directories. We could come up with some regex type thing but that seems fragile. There likely won't be many config changes to past release lines, so it is probably ok to leave it as just the master branch of ozone and ozone-site for now. -- 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]
