Hi -

We need to tighten up our procedures around releases. There are several issues.

1. Maintaining the official KEYS file - 
https://dist.apache.org/repos/dist/release/pulsar/KEYS

During the pulsar-manager-0.3.0 release the KEYS were not updated from 
https://dist.apache.org/repos/dist/dev/pulsar/KEYS This was flagged by ASF 
Infra and I’ve updated the KEYS file to contain both urfree’s and 
mattisonchao’s keys. (We should be good for 2.9.3)

I suggest that we delete https://dist.apache.org/repos/dist/dev/pulsar/KEYS and 
only use the official https://dist.apache.org/repos/dist/release/pulsar/KEYS in 
all cases. We will need to rewrite our release docs.

2, We often leave old releases in the distribution directory. I’ve cleaned 
these up, but we need to make sure that this is documented for everything that 
is officially released.

./pulsar-client-node/pulsar-client-node-1.6.2
./pulsar-2.10.1
./pulsar-2.10.1/connectors
./pulsar-2.10.1/RPMS
./pulsar-2.10.1/RPMS/repodata
./pulsar-2.10.1/DEB
./pulsar-2.9.2
./pulsar-2.9.2/connectors
./pulsar-2.9.2/RPMS
./pulsar-2.9.2/RPMS/repodata
./pulsar-2.9.2/DEB
./pulsar-adapters-2.8.0
./pulsar-client-go-0.8.1
./pulsar-manager/pulsar-manager-0.3.0
./pulsar-2.8.3
./pulsar-2.8.3/connectors
./pulsar-2.8.3/RPMS
./pulsar-2.8.3/RPMS/repodata
./pulsar-2.8.3/DEB

3. Pulsar 2.7.4 was removed from the Release distribution on January 20, 2022. 
Did we announce the EOL of 2.7.x? I don’t recall, but it’s easy to miss 
activity.

4. If the Apache Pulsar Helm Chart and Apache Pulsar Docker Images are intended 
to be official convenience releases then they must be included into 
https://dist.apache.org/repos/dist/release/pulsar/.

a) The Helm Chart is not under any ASF process and there needs to be a whole 
separate discussion about properly handling it.

b) What is the deal with the docker images? What is the current process? Why 
can’t we add them in the release repository where anyone can downstream them to 
a convenient location.

All The Best,
Dave

Reply via email to