thetumbled commented on PR #23199: URL: https://github.com/apache/pulsar/pull/23199#issuecomment-2301860034
> @thetumbled Before merging a PR, please take care to label the releases where the PR should also be applied. The current process works in a way where we add release labels for the next pending releases so that we remember to cherry-pick the fix to maintenance branches. We should always pick non-breaking fixes to the supported maintenance version branches. Currently it's branch-3.0 and branch-3.3. Right now this means adding labels `release/3.0.7` and `release/3.3.2` to the PR. During cherry-picking, these labels are used to search the PRs that need to be cherry-picked. Some of this process is explained in https://pulsar.apache.org/contribute/release-process/#cherry-picking-changes-scheduled-for-the-release . > > I've been recently using these shell script functions: [https://github.com/lhotari/pulsar-contributor-toolbox/blob/33effd94d38c5d2b0ddad70[…]f034f62c425fe/functions/pulsar-contributor-toolbox-functions.sh](https://github.com/lhotari/pulsar-contributor-toolbox/blob/33effd94d38c5d2b0ddad700790f034f62c425fe/functions/pulsar-contributor-toolbox-functions.sh#L1392-L1415) and [https://github.com/lhotari/pulsar-contributor-toolbox/blob/33effd94d38c5d2b0ddad70[…]f034f62c425fe/functions/pulsar-contributor-toolbox-functions.sh](https://github.com/lhotari/pulsar-contributor-toolbox/blob/33effd94d38c5d2b0ddad700790f034f62c425fe/functions/pulsar-contributor-toolbox-functions.sh#L1443-L1454) . They help a lot in handling the cherry-picking. Slightly improved compared to what I documented in https://pulsar.apache.org/contribute/release-process/#cherry-picking-changes-scheduled-for-the-release. Thanks for explaining. -- 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]
