You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by guo jiwei <te...@apache.org> on 2024/01/27 15:14:27 UTC
[VERIFY] Pulsar Release 3.2.0 Candidate 5
This is the fifth release candidate for Apache Pulsar version 3.2.0.
It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1
*** Please download, test and verify on this release. This release
candidate verification will stay open until Feb 2 ***
Note that we are verifying upon the source (tag), binaries are provided for
convenience.
Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
SHA-512 checksums:
194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
apache-pulsar-3.2.0-bin.tar.gz
7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
apache-pulsar-3.2.0-src.tar.gz
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1265/
The tag to verify:
v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS
Docker images:
pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
<https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore>
pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.
Regards
Jiwei Guo (Tboy)
Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5
Posted by guo jiwei <te...@apache.org>.
> I think we need to state the release deadline before each feature
release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the vote
now?
Yes, I will raise the `VOTE` thread soon.
Regards
Jiwei Guo (Tboy)
On Tue, Jan 30, 2024 at 9:55 AM Zike Yang <zi...@apache.org> wrote:
> Based on the release
> policy(https://pulsar.apache.org/contribute/release-policy/), for each
> feature release, there would be three weeks to verify the release
> candidate before the release deadline. And the first two weeks are
> only for verification.
>
> I think we need to state the release deadline before each feature
> release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the
> vote now?
>
> > We don't have that in our release process documented at
> https://pulsar.apache.org/contribute/release-process/ .
>
> Indeed, we need to add this guidance into the release process to align
> it with the release policy.
>
> Thanks,
> Zike Yang
>
> On Mon, Jan 29, 2024 at 11:25 PM Lari Hotari <lh...@apache.org> wrote:
> >
> > Is this a release VOTE thread? I think that the subject of the thread
> should state that explicitly.
> >
> > What does a VERIFY thread mean? We don't have that in our release
> process documented at
> https://pulsar.apache.org/contribute/release-process/ .
> >
> > Thanks,
> >
> > -Lari
> >
> > On 2024/01/27 15:14:27 guo jiwei wrote:
> > > This is the fifth release candidate for Apache Pulsar version 3.2.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar/milestone/36?closed=1
> > >
> > > *** Please download, test and verify on this release. This release
> > > candidate verification will stay open until Feb 2 ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are
> provided for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
> > >
> > > SHA-512 checksums:
> > >
> > >
> 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
> > >
> > > apache-pulsar-3.2.0-bin.tar.gz
> > >
> > >
> 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
> > >
> > > apache-pulsar-3.2.0-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1265/
> > >
> > > The tag to verify:
> > > v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > > pulsar images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> > > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > > pulsar-all images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > > Note that this RC doesn't require a formal vote, but we would also
> > > appreciate your feedback with +1/-1. And please provide specific
> > > comments if your feedback is not +1.
> > >
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
>
Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5
Posted by Zike Yang <zi...@apache.org>.
Based on the release
policy(https://pulsar.apache.org/contribute/release-policy/), for each
feature release, there would be three weeks to verify the release
candidate before the release deadline. And the first two weeks are
only for verification.
I think we need to state the release deadline before each feature
release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the
vote now?
> We don't have that in our release process documented at https://pulsar.apache.org/contribute/release-process/ .
Indeed, we need to add this guidance into the release process to align
it with the release policy.
Thanks,
Zike Yang
On Mon, Jan 29, 2024 at 11:25 PM Lari Hotari <lh...@apache.org> wrote:
>
> Is this a release VOTE thread? I think that the subject of the thread should state that explicitly.
>
> What does a VERIFY thread mean? We don't have that in our release process documented at https://pulsar.apache.org/contribute/release-process/ .
>
> Thanks,
>
> -Lari
>
> On 2024/01/27 15:14:27 guo jiwei wrote:
> > This is the fifth release candidate for Apache Pulsar version 3.2.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar/milestone/36?closed=1
> >
> > *** Please download, test and verify on this release. This release
> > candidate verification will stay open until Feb 2 ***
> >
> > Note that we are verifying upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
> >
> > SHA-512 checksums:
> >
> > 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
> >
> > apache-pulsar-3.2.0-bin.tar.gz
> >
> > 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
> >
> > apache-pulsar-3.2.0-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1265/
> >
> > The tag to verify:
> > v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> > https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Docker images:
> >
> > pulsar images:
> > https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> > <https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore>
> > pulsar-all images:
> > https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> > Note that this RC doesn't require a formal vote, but we would also
> > appreciate your feedback with +1/-1. And please provide specific
> > comments if your feedback is not +1.
> >
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5
Posted by Lari Hotari <lh...@apache.org>.
Is this a release VOTE thread? I think that the subject of the thread should state that explicitly.
What does a VERIFY thread mean? We don't have that in our release process documented at https://pulsar.apache.org/contribute/release-process/ .
Thanks,
-Lari
On 2024/01/27 15:14:27 guo jiwei wrote:
> This is the fifth release candidate for Apache Pulsar version 3.2.0.
>
> It fixes the following issues:
> https://github.com/apache/pulsar/milestone/36?closed=1
>
> *** Please download, test and verify on this release. This release
> candidate verification will stay open until Feb 2 ***
>
> Note that we are verifying upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
>
> SHA-512 checksums:
>
> 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
>
> apache-pulsar-3.2.0-bin.tar.gz
>
> 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
>
> apache-pulsar-3.2.0-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1265/
>
> The tag to verify:
> v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> <https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore>
> pulsar-all images:
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> Note that this RC doesn't require a formal vote, but we would also
> appreciate your feedback with +1/-1. And please provide specific
> comments if your feedback is not +1.
>
>
>
> Regards
> Jiwei Guo (Tboy)
>
Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5
Posted by PengHui Li <pe...@apache.org>.
+1 (binding)
- Built from source
- Checked the signatures
- Run standalone
- Checked producer and consumer
- Verified the Cassandra connector
- Verified the Stateful function
Regards,
Penghui
On Sat, Jan 27, 2024 at 11:15 PM guo jiwei <te...@apache.org> wrote:
> This is the fifth release candidate for Apache Pulsar version 3.2.0.
>
> It fixes the following issues:
> https://github.com/apache/pulsar/milestone/36?closed=1
>
> *** Please download, test and verify on this release. This release
> candidate verification will stay open until Feb 2 ***
>
> Note that we are verifying upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
>
> SHA-512 checksums:
>
>
> 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
>
> apache-pulsar-3.2.0-bin.tar.gz
>
>
> 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
>
> apache-pulsar-3.2.0-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1265/
>
> The tag to verify:
> v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
>
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> pulsar-all images:
>
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> Note that this RC doesn't require a formal vote, but we would also
> appreciate your feedback with +1/-1. And please provide specific
> comments if your feedback is not +1.
>
>
>
> Regards
> Jiwei Guo (Tboy)
>