lhotari commented on PR #23199: URL: https://github.com/apache/pulsar/pull/23199#issuecomment-2301873505
> Thanks for explaining. @thetumbled The cherry-picking process isn't properly documented. There's a thread https://lists.apache.org/thread/j6qvt45rndnvjypcmqxsfmddqt41bxjv about improving and changing it. In the current process it's sufficient to add the labels while merging. The committers actively working as release managers will handle cherry-picking and backporting and request for specific backports when a PR cannot be easily backported while resolving merge conflicts in cherry-picking. It's very common that there are merge conflicts and it's necessary to understand the tooling and process to handle the merge conflict resolution. The guide https://pulsar.apache.org/contribute/setup-git/ contains some suggestions for setting up git for maintaining Pulsar. If you are interested in the release manager role of one of the next Pulsar releases, you can suggest it on the dev mailing list or express interest on the Pulsar Slack #dev channel. I'm one of the committers who can you can also ping on Pulsar Slack #dev channel to help with various Pulsar release maintenance tasks. I'm looking for volunteers to help with these tasks. -- 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]
