Thanks for the validation.
Close this vote with 3 +1(binding), 2 +1(non-binding)
I will start the subsequent release work soon.
Thanks,
Yong
On Mon, 15 Mar 2021 at 09:55, Jia Zhai wrote:
> +1 (binding)
>
> OS: MacOS 10.15.6
>
> - verified packages checksum and signatures ( asc and sha all goo
+1 (binding)
OS: MacOS 10.15.6
- verified packages checksum and signatures ( asc and sha all good)
- the source package rat check(mvn apache-rat:check), licence check, build
and unit test all run successfully.
- bin package build from source, 'bin/pulsar standalone' and client
produce/consume ru
+1 (binding)
1. LICENSE / NOTICE / Checksum / Signature are good
2. Source package can be compiled
3. Binary package is good with functionalities (pub/sub, functions,
connectors) verified.
- Sijie
On Fri, Mar 12, 2021 at 10:13 AM Henry Saputra
wrote:
> Verify the source release artifact:
> L
Verify the source release artifact:
LICENSE file looks good
NOTICE file needs to update the year to 2021 -> Not release blocker but
need to be fixed in the branch since master already updated.
Checksum files look good
Signature file looks good
License header in source looks good (Maven Ra
+1 (binding)
1. Start standalone
2. Produce and consume messages
3. Verify Cassandra connector
4. Verify stateful Functions
5. Verify Pulsar SQL
Thanks,
- Penghui
Enrico Olivelli 于2021年3月12日周五 下午2:32写道：
> Thank you Yong for putting this together
>
> +1 (non binding)
>
> - Checked artifacts/che
Thank you Yong for putting this together
+1 (non binding)
- Checked artifacts/checksums/signs
- Built from sources on JDK8/MacOs
- Run smoke tests on JDK8/MacOs
- Passed integration tests of DataStax Pulsar Cassandra Sink (using
Docker image)
- Passed internal system tests:
- including:
* Dock
Hi Yong, Yes, the files can be different in dev and releases directory, but
the artifact files prepared for releases should be signed using key exist
in both directories.
If PMC are vetting on release artifacts [1], including validating the
signature, it needs to use the same key to sign it.
Prefe
Thanks Penghui.
Henry,
the /dev/ directory can be accessed by all committers, so the committers
can add themself keys into the KEYS file. But the /release/ directory only
can be accessed by PMCs, the committers need to let PMC help to add
their key into the release directory. It's ok if the KEYS f
@yong I have add your key to the /release directory.
Thanks,
Penghui
On Mar 10, 2021, 3:24 AM +0800, Henry Saputra , wrote:
> Why does the KEYS file for /dev/ is different from the one in /release/
> directory?
>
> When users download the artifact they will verify against the one in
> /release/ d
Why does the KEYS file for /dev/ is different from the one in /release/
directory?
When users download the artifact they will verify against the one in
/release/ directory, right?
- Henry
On Tue, Mar 9, 2021 at 2:48 AM Yong Zhang
wrote:
> For the signature issue, I think we should use this key
For the signature issue, I think we should use this keys
https://dist.apache.org/repos/dist/dev/pulsar/KEYS
I updated the Pulsar release process
https://github.com/apache/pulsar/wiki/Release-process#8-run-the-vote
The keys in the file https://dist.apache.org/repos/dist/release/pulsar/KEYS
are the
Yong,
I cannot build the docker image from the sources extracted by the
source tarball.
This is probably a big issue, because as I cannot build the docker
image I cannot run tests on downstream applications.
I am not sure this was possible with 2.7.0, so I don't know if this is
a blocker for the
Yong,
I cannot find your signature at
https://dist.apache.org/repos/dist/release/pulsar/KEYS
can you please add yourself ?
otherwise I cannot validate the digital signatures of the artifacts
Thanks
Enrico
Il giorno lun 8 mar 2021 alle ore 05:41 Yong Zhang ha scritto:
>
> Hi all.
>
> This is the
Hi all.
This is the first release candidate for Apache Pulsar, version 2.X.0.
It fixes the following issues:
https://github.com/apache/pulsar/pulls?page=1&q=is%3Apr+label%3Arelease%2F2.7.1+is%3Aclosed+-label%3Acomponent%2Fdocumentation
*** Please download, test and vote on this release. This vot
14 matches
Mail list logo
