Hi Enrico Olivell, When you need to release a package, it is important to follow the release manual. Here is a summary of the steps you need to take:
1. Update the version and tag of a package. 2. Create a GitHub prerelease. 3. Download the source code. 4. Sign and stage the artifacts. 5. Run a vote. 6. Summary of vote. 7. Promote the release. 8. Create a GitHub release. 9. Announce the release. Step 5 is the voting phase, where the release is approved or rejected. You can find the full release manual by checking out the PR mentioned in the first email. Sincerely, David Jensen On 2023/10/30 07:08:20 Enrico Olivelli wrote: > How do we handle the VOTE? > > Enrico > > Il Lun 30 Ott 2023, 08:06 Zike Yang <zi...@apache.org> ha scritto: > > > Hi, David > > > > Thanks for initializing this discussion. > > I'm +1 for making the auto-release process for the DotPulsar. I have > > left some comments in the PR. > > > > Thanks, > > Zike Yang > > > > On Thu, Oct 26, 2023 at 5:39 PM David Jensen <en...@gmail.com> wrote: > > > > > > Hi everyone, > > > I have worked with Tison to make the release process smoother for > > DotPulsar > > > <https://github.com/apache/pulsar-dotpulsar>. See GitHub Issue #184 > > Release > > > process and GitHub Action > > > <https://github.com/apache/pulsar-dotpulsar/pull/184> and the linked > > issues. > > > > > > In summary, the document presents a suggested approach for creating > > release > > > notes and optimizing the release workflow of the Pulsar C# Client. This > > > approach involves working closely with team members, adhering to ASF > > > guidelines, participating in Apache release voting, implementing > > automation > > > via GitHub Actions, and managing versioning through git tags and GitHub > > > releases. > > > > > > Sincerely > > > David Jensen > > >
