Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 1

2023-11-02 Thread Baodi Shi
 +1 (non-binding)

-  Checked the sign and checksum
-  Build the source
-  Test SampleProducer and SampleConsumer

Thanks,
Baodi Shi


On Nov 1, 2023 at 18:18:21, Yunze Xu  wrote:

> This is the first release candidate for Apache Pulsar Client C++, version
> 3.4.0.
>
> It fixes the following issues:
> https://github.com/apache/pulsar-client-cpp/milestone/5?closed=1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-cpp/pulsar-client-cpp-3.4.0-candidate-1/
>
> SHA-512 checksums:
>
>
> 85c2ae95bb3abb7c13326e1205c4dc9e339387d13efab242e51c044c53d322a65a28d32928ebe53202ea59f2df46a74480c4ef675e25adc64c14025dc3e314aa
> ./apache-pulsar-client-cpp-3.4.0.tar.gz
>
> The tag to be voted upon:
> v3.4.0-candidate-1 (272e1a1c78fd72d80758ac56ce400c67ce54d167)
> https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.0-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Please download the source package, and follow the README to compile and
> test.
>


Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar

2023-11-02 Thread tison
> 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#pullrequestreview-1710708673
.

Best,
tison.


Enrico Olivelli  于2023年10月30日周一 15:09写道:

> 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:39 PM David Jensen  wrote:
> > >
> > > Hi everyone,
> > > I have worked with Tison to make the release process smoother for
> > DotPulsar
> > > . See GitHub Issue #184
> > Release
> > > process and GitHub Action
> > >  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
> >
>


Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar

2023-11-02 Thread tison
> 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 request as it's a net win compared to DotPulsar's
> current status; see
> https://github.com/apache/pulsar-dotpulsar/pull/184#pullrequestreview-1710708673
> .
>
> Best,
> tison.
>
>
> Enrico Olivelli  于2023年10月30日周一 15:09写道:
>
>> 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:39 PM David Jensen  wrote:
>> > >
>> > > Hi everyone,
>> > > I have worked with Tison to make the release process smoother for
>> > DotPulsar
>> > > . See GitHub Issue #184
>> > Release
>> > > process and GitHub Action
>> > >  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
>> >
>>
>