Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc] Update the release process about how to release C++ and Python client #17918

Closed
1 of 2 tasks
Tracked by #5065 ...
tisonkun opened this issue Oct 4, 2022 · 9 comments
Closed
1 of 2 tasks
Tracked by #5065 ...
Labels
doc-required Your PR changes impact docs and you will update later.

Comments

@tisonkun
Copy link
Member

tisonkun commented Oct 4, 2022

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

After #17724 moves pulsar-client-cpp and pulsar-client-python to new repository, the original release process is no longer valid.

What is your suggestion?

cc @merlimat @BewareMyPower @shibd @RobertIndie

IIRC these two clients have their own release cycle, thus the issue here can be simply to remove the related sections in the current release process and then write the new one in each repo.

Any reference?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@Anonymitaet
Copy link
Member

Hi @merlimat @BewareMyPower

Currently (2.8.4), even though C++ and Python are moved out of the main Pulsar repo, their release notes are still together with the Pulsar core.

image

In the future, will the release notes of C++ and Python be in their repos and not bundled in the main Pulsar repo? Just like Go, C#, and Node.js?

image

image

Thanks for your answer!

🔹🔹🔹

More context:

I ask this because we (@SignorMercurio @urfreespace) are implementing #17310

We need to change the workflow if the source truth of release notes is changed.

@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

@tisonkun
Copy link
Member Author

IIRC @BewareMyPower is going to update the C++ release process after 3.1.0 released. @BewareMyPower could you create a corresponding subtask in https://github.com/apache/pulsar-client-cpp?

@BewareMyPower
Copy link
Contributor

Created: apache/pulsar-client-cpp#123

@tisonkun
Copy link
Member Author

@BewareMyPower @RobertIndie @shibd

For the C++ client, we have https://github.com/apache/pulsar-client-cpp/wiki/Committer-Release-Guide now. What about the Python client?

@BewareMyPower
Copy link
Contributor

@tisonkun I will write the process after the Python client 3.0.0 is out.

@tisonkun
Copy link
Member Author

@BewareMyPower Thank you! If you'd like to create it in the https://github.com/apache/pulsar-client-python repo, can you open an issue there and let's close this as superseded by dedicated issues?

@BewareMyPower
Copy link
Contributor

@tisonkun It's opened now: apache/pulsar-client-python#64

@tisonkun
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required Your PR changes impact docs and you will update later.
Projects
None yet
Development

No branches or pull requests

3 participants