> the formal release
to release artifacts of a formal version (no -rc).
Best,
tison.
tison 于2023年11月3日周五 00:13写道：
> > How do we handle the VOTE?
>
> It's recorded in the process doc. Basically, the formal release will be
> triggered once the vote on list gets passed.
>
> I've merged the pull
> How do we handle the VOTE?
It's recorded in the process doc. Basically, the formal release will be
triggered once the vote on list gets passed.
I've merged the pull request as it's a net win compared to DotPulsar's
current status; see
https://github.com/apache/pulsar-dotpulsar/pull/184#pullrequ
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
Thanks for the feedback. I have to respond to your question on GitHub. :)
On 2023/10/30 07:05:46 Zike Yang wrote:
> 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
How do we handle the VOTE?
Enrico
Il Lun 30 Ott 2023, 08:06 Zike Yang 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
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 wrote:
>
> Hi everyone,
> I have worked with Tison to make the release process smo
