Hello all committers: During release 2.4.2, there are some questions I want to share with you, see how to further improve our release process.
One: Currently for the minor version of the bug fix, e.g: v2.4.2. We are based on the `branch-2.4`, execute `cherry-pick` to merge the pull requests into branch-2.4. This process is very painful, details as follows: - Since the 2.4.2 version is only a bug fix to the 2.4.0 and 2.4.1 versions, we cannot cherry-pick the changes related to the protocol, interface, etc to the 2.4.2 version. But some pull requests that belong to 2.4.2 are based on these changes, In 2.4.2, we can only split these changes again and send a new pull request. In here, do we have a reasonable solution to this problem? Two: Currently, the test check of branch not work, there are two main problems: - the java8 tests missing - the cpp tests not work Maybe we can start the branch function to ensure that each branch is in a working state. Three: there are some confuse in the release process documentation. About this, I have update the release process documentation. -- Thanks Xiaolong Ran
