This is an automated email from the ASF dual-hosted git repository. lhotari pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit 9057e05e49263012fde610fcd31d7b240a9eff88 Author: Lari Hotari <[email protected]> AuthorDate: Fri Jun 12 02:47:30 2026 +0300 Remove obsolete Homebrew libpulsar and Python client release sections These steps only applied to Pulsar 2.8-2.10 releases; the C++ and Python clients now live in separate repositories with their own release guides. --- contribute/release-process.md | 64 ------------------------------------------- 1 file changed, 64 deletions(-) diff --git a/contribute/release-process.md b/contribute/release-process.md index db3084d6622..f0c3f03b7ec 100644 --- a/contribute/release-process.md +++ b/contribute/release-process.md @@ -670,70 +670,6 @@ This step is for the latest *LTS* release only 3. Send a pull request for reviews and get it merged. 4. Once it is merged, the chart will be automatically released to GitHub releases at https://github.com/apache/pulsar-helm-chart and updated to https://pulsar.apache.org/charts/index.yaml. -### Release Homebrew libpulsar package - -For 2.8, 2.9 and 2.10 releases, you should release the libpulsar package on Homebrew. - -:::caution - -The C++ client is now developing in a [separated repo](https://github.com/apache/pulsar-client-cpp). You should check its own release guide if you're releasing version >= 3.0.0. - -::: - -Release a new version of libpulsar for Homebrew, You can follow the example [here](https://github.com/Homebrew/homebrew-core/pull/53514). - -### Release Python client - -For 2.8, 2.9 and 2.10 releases, you should release the Python client. - -:::note - -1. You need to create an account on PyPI: https://pypi.org/account/register/ -2. Ask anyone that has been a release manager before to add you as a maintainer for pulsar-docker on PyPI -3. Once you have completed the following steps in this section, you can check if the wheels are uploaded successfully in [Download files](https://pypi.org/project/pulsar-client/#files). Remember to switch to the correct version in [Release history](https://pypi.org/project/pulsar-client/#history). - -::: - -:::caution - -Make sure you run following command at the release tag! - -::: - -:::caution - -The Python client is now developing in a [separated repo](https://github.com/apache/pulsar-client-python). You should check its own release guide if you're releasing version >= 3.0.0. - -::: - -#### Linux - -There is a script that builds and packages the Python client inside Docker images: - -```shell -pulsar-client-cpp/docker/build-wheels.sh -``` - -The wheel files will be left under `pulsar-client-cpp/python/wheelhouse`. Make sure all the files have `manylinux` in the filenames. Otherwise, those files will not be able to upload to PyPI. - -Run the following command to push the built wheel files: - -```shell -cd pulsar-client-cpp/python/wheelhouse -pip install twine -twine upload pulsar_client-*.whl -``` - -#### macOS - -There is a script that builds and packages the Python client inside Docker images: - -```shell -pulsar-client-cpp/python/build-mac-wheels.sh -``` - -The wheel files will be generated at each platform directory under `pulsar-client-cpp/python/pkg/osx/`. Then you can run `twin upload` to upload those wheel files. - ## Update the document ### Release notes
