I’ve updated the release process in https://github.com/apache/pulsar-client-cpp/wiki/Committer-Release-Guide#sign-and-stage-the-artifacts
Feel free to update the release process if you have any other idea. Thanks, Yunze > On Mar 25, 2024, at 20:39, Baodi Shi <ba...@apache.org> wrote: > > +1 Thank you for push this discussion. > > We can modify the release process: we'll require the release manager to > attach the PR for Python and Node.js upgrades when initiating a candidate > vote, and ensure it CI can pass. > > Once the CPP client release is successful, we can remove the candidate, and > then push for its merge. > > > Thanks, > Baodi Shi > > > On Mar 25, 2024 at 18:29:23, Yunze Xu <x...@apache.org> wrote: > >> Hi all, >> >> Recently I found a regression [1] for the C++ client 3.5.0 (thanks to >> the reminder from @shibd). So I will push a fix and then release the >> C++ client 3.5.1. >> >> However, this is not the 1st time that a regression was introduced, >> see [2] for example. So I suggest when verifying the C++ client, we >> can verify the Python and Node.js clients by upgrading the >> dependencies as well. See the updated release process in [3]. >> >> [1] https://github.com/apache/pulsar-client-cpp/issues/420 >> [2] https://lists.apache.org/thread/rjolgrlp4x1lmfj678k3hjco80kcb73c >> [3] >> https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env#verify-the-3rd-party-projects-that-depend-on-pulsar-c-client >> >> Thanks, >> Yunze >>
