+1 (binding) Did my usual tests and verified signatures and hashes.
> Am 19.07.2026 um 17:00 schrieb Rui Abreu <[email protected]>: > > Tested with storm-docker downloading the RC binaries. > > Standard distribution: > > - Submitted org.apache.storm.kafka.spout.KafkaSpoutTopologyMainNamedTopics > from storm-examples. Producers and consumers work normally, no errors. > > Lite distribution: > > - Submitted org.apache.storm.starter.LambdaTopology from storm-examples. > Works well. > > - Submitted org.apache.storm.kafka.spout.KafkaSpoutTopologyMainNamedTopics > from storm-examples. Producers and consumers work well. > > - Kafka spout lag is not displayed in the UI when storm-kafka-monitor is > absent, as expected. The UI logs: > > "Kafka spout lag monitoring is unavailable because the > storm-kafka-monitor jars are not installed. They ship only in the full > binary distribution; on the lite distribution run > 'bin/storm-kafka-monitor-fetch' on the UI host (and restart the UI) > to enable it." > > - Tested bin/storm-kafka-monitor-fetch by installing Maven in the container > and pointing it at the Nexus staging repository: > > apt-get install -y --no-install-recommends maven > > cat > /tmp/staging-settings.xml <<EOF > <settings> > <profiles><profile><id>staging</id> > <repositories><repository> > <id>apache-staging</id> > > <url>https://repository.apache.org/content/repositories/orgapachestorm-1128</url> > </repository></repositories> > </profile></profiles> > <activeProfiles><activeProfile>staging</activeProfile></activeProfiles> > </settings> > EOF > > /apache-storm/bin/storm-kafka-monitor-fetch -- -s /tmp/staging-settings.xml > > After restarting the UI (docker restart ui), Kafka spout lag is > displayed correctly. > > Signatures and checksums verified. > > > +1 binding > > > > On Sun, 19 Jul 2026 at 14:40, Rui Abreu <[email protected]> wrote: >> >> Hi folks, >> >> I have posted the 2nd release candidate for Apache Storm 3.0.0 >> release and it is ready for testing. >> >> The Nexus staging repository is here: >> https://repository.apache.org/content/repositories/orgapachestorm-1128 >> >> Storm Source and Binary Release with sha512 signature files are here: >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-3.0.0-rc2/ >> >> The release artifacts are signed with the following key: >> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x72B436558AA9CDCA2C4CBAC340D4B35E2C1452E5 >> in this file https://www.apache.org/dist/storm/KEYS >> >> The release was made from the Apache Storm 3.0.0 tag at: >> https://github.com/apache/storm/tree/v3.0.0 >> >> Full list of changes in this release: >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-3.0.0-rc2/RELEASE_NOTES.html >> >> To use it in a Maven build set the version for Storm to 3.0.0 and add >> the following URL to your settings.xml file: >> https://repository.apache.org/content/repositories/orgapachestorm-1128 >> >> The release was made using the Storm release process, documented on >> the GitHub repository: >> https://github.com/apache/storm/blob/master/RELEASING.md >> >> Please vote on releasing these packages as Apache Storm 3.0.0. The >> vote is open for at least the next 72 hours. >> >> "How to vote" is described here: >> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate >> When voting, please list the actions taken to verify the release. >> >> Only votes from the Storm PMC are binding, but everyone is welcome to >> check the release candidate and vote. >> The vote passes if at least three binding +1 votes are cast. >> >> [ ] +1 Release this package as Apache Storm 3.0.0 >> [ ] 0 No opinion >> [ ] -1 Do not release this package because... >> >> Thanks to everyone who contributed to this release.
