One of the challenges I have seen in the release process is how to merge a pull request to multiple branches for multiple releases. Especially the community has grown very fast, I can see multiple concurrent release efforts. Hence I would strongly recommend adopting the merge flow from BookKeeper and adjust it to fit into the Pulsar development cycle. This can address many pain points we have seen in the release process.
- Sijie On Tue, Dec 17, 2019 at 1:18 PM Jia Zhai <zhaiji...@gmail.com> wrote: > Thanks @xiaolong for rising up this discussion. > Apache BookKeeper uses a script to do the PR merge, and the script could > handle cherry-pick into old branch if needed. This could avoid cherry-pick > at the release time. > > > Best Regards. > > > Jia Zhai > > Beijing, China > > Mobile: +86 15810491983 > > > > > On Tue, Dec 10, 2019 at 3:57 PM xiaolong ran <ranxiaolong...@gmail.com> > wrote: > > > In PIP-47, we have adopted the Time Based Release Plan, > > If we can improve our release process, we will run it better. > > > > -- > > Thanks > > Xiaolong Ran > > > > > > > 在 2019年12月10日，下午3:54，xiaolong ran <ranxiaolong...@gmail.com> 写道： > > > > > > 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 > > > > > > > > > > > > > > > > > > > >
