linghengqian commented on issue #30754: URL: https://github.com/apache/shardingsphere/issues/30754#issuecomment-2034142992
> I decide to suggest about clearly writing out that memory mode was replaced by standalone mode in normal and direct place like offcial release log or document, not just in issues list. > That's all why I submit this issue. > > BYW, I know that code after tagging cannot be changed again, but official examples with obivious errors (like examples in V5.2.0/V5.2.1 still using memory mode) are very confusing. Maybe there can be some way to resolve this situation - There are two common practices under normal circumstances. One is to always have a documentation page on the master branch's documentation to point out the breaking changes across versions, like Apache Seata does. But in fact, almost no one on the Committer team has time to read thousands of PRs and issues for a single milestone, which is usually what the release manager does. The current practice of shardingsphere is similar to `zstd-jni`, but there is a general release summary text for github release. Refer to https://github.com/luben/zstd-jni . Affected by the AI specification of ASF, it is difficult to say whether this text can be allowed to be generated by tools such as ChatGPT. - For the example module, the development of this module is relatively independent, because normal PR changes will not trigger the CI of the example module, which explains some strange phenomena. There is only nightly CI for the example module, and the current nightly CI of the example module still has problems. PR is welcome. - I am not the author of the release note at https://github.com/apache/shardingsphere/releases/tag/5.2.0 , so I will ask the PMC who completed the github release. What do you think? CC @strongduanmu . -- 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]
