Anonymitaet commented on code in PR #17990: URL: https://github.com/apache/pulsar/pull/17990#discussion_r991790632
########## wiki/release/release-note-guide.md: ########## @@ -0,0 +1,69 @@ +This guide explains everything about Pulsar release notes. + +# Intro to release notes + +This chapter gives an overview of Pulsar release notes. + +## Basic info + +[Pulsar release notes](https://pulsar.apache.org/release-notes/) consist of the following parts. + +Release note | Component +---|--- +[Pulsar core](https://pulsar.apache.org/release-notes/#pulsar-release-notes)| Pulsar +[Pulsar clients](../../site2/docs/client-libraries.md) |- Java <br><br> - WebSocket <br><br> - C++ <br><br> - Python <br><br> - Go <br><br> - NodeJs <br><br> - C# + +## Maintenance info + +For the [Pulsar Release Note page](https://pulsar.apache.org/release-notes/): + +- It is generated automatically using [release-json-gen.sh](https://github.com/apache/pulsar-site/blob/main/site2/tools/release-json-gen.sh). + + For implementation details, see [PIP 112: Generate Release Notes Automatically](https://github.com/apache/pulsar/wiki/PIP-112:-Generate-Release-Notes-Automatically). + +- The info is fetched from the [Pulsar Releases Page - GitHub](https://github.com/apache/pulsar/releases). + +- It is updated when one of the following conditions is met: + + - A commit is pushed to the [pulsar-site repo](https://github.com/apache/pulsar-site). + + - A [Pulsar site sync job](https://github.com/apache/pulsar-site/actions/workflows/ci-pulsar-website-docs-sync.yaml) is performed (every 6 hours). + +# Submit release notes + +Follow the steps below to submit release notes for Pulsar and clients. + +1. On the [Pulsar Releases Page - GitHub](https://github.com/apache/pulsar/releases), add a release note for the new release. + + <table> + <thead> + <tr> + <th colspan="2">Component</th> + <th>Step</th> + </tr> + </thead> + <tbody> + <tr> + <td colspan="2">Pulsar core</td> + <td>Add a release note for it.</td> + </tr> + <tr> + <td rowspan="2">Pulsar clients</td> + <td> - Java<br><br> - WebSocket<br><br> - C++<br><br> - Python</td> + <td>Add separate release notes for them, that is, create independent sections in the release note.<br><br>Example<br><br><img title="Java client release note example" alt="Java client release note example" src="../assets/release-note-guide-1.png"></td> + </tr> + <tr> + <td> - Go<br><br> - Node.js<br><br> - C#</td> + <td>No action is needed. You do not need to take care of them since their release notes are synced from their repos to the <a href="https://pulsar.apache.org/release-notes/";>Pulsar Release Note page</a>.</td> + </tr> + </tbody> + </table> Review Comment: Markdown tables do not support complex format (eg. "merge cells"), so I use HTML instead. <img width="595" alt="image" src="https://user-images.githubusercontent.com/50226895/194993764-66dd42b8-8c7d-4ce6-93b9-a85fb3d26d5f.png";> -- 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]
![https://user-images.githubusercontent.com/50226895/194993764-66dd42b8-8c7d-4ce6-93b9-a85fb3d26d5f.png"](https://user-images.githubusercontent.com/50226895/194993764-66dd42b8-8c7d-4ce6-93b9-a85fb3d26d5f.png"){kind=link}