+1 (binding)
Thanks for putting this together, Davide.
Checked on macOS (aarch64), Temurin 25.0.3, Maven 3.9.16:
[X] Artifacts present: source tar.gz and zip, each with .asc and .sha512.
No binary convenience artifacts, which matches what 3.6.0 shipped.
[X] PGP signatures valid and that key is present in the
KEYS file at https://downloads.apache.org/stormcrawler/KEYS
[X] SHA512 checksums match for both archives.
[X] Commit hash matches the stormcrawler-3.7.0 tag.
The source tarball is identical to the tag
contents, the only addition being the generated DEPENDENCIES file.
[X] No SNAPSHOT versions in any pom, storm-client.version is 2.8.9 as
announced.
[X] LICENSE (plain ALv2) and NOTICE present.
[X] No unexpected binaries in the source release. The only non-text
files are legitimate test fixtures (warc.gz, sitemap.xml.gz, a
test .docx) and the two doc images. No jars or class files.
[X] Build completes from source: mvn clean install -DskipTests passes.
The build requirements in README.md (JDK 17+, Maven 3, Docker for
tests) are clear. Note I skipped the test run, so I have not
exercised the testcontainers-based suite.
[X] Staged Maven artifacts resolve and are signed: verified core, tika,
urlfrontier and warc all have pom, jar and valid .asc in
orgapachestormcrawler-1038.
Beyond the checklist, I ran an end-to-end crawl against the staging
repository using my WARC demo project:
https://github.com/rzo1/sc-warc-demo/tree/test-stormcrawler-3.7.0-rc1
Caveat on that test: the demo topology comes from the 3.5.x archetype
and does not wire up the new queue stream, so the URLFrontier back-off
and Crawl-delay handling that headlines this release was not exercised
by my run.
One minor nits, neither a blocker:
1. NOTICE still reads "Copyright 2025 The Apache Software Foundation".
3.6.0 said 2025 and was released in 2025, so this looks like it was
simply not refreshed for a 2026 release. Worth fixing whenever the
next RC or 4.0 comes around, no need to respin for it.
On the website question: yes, please state the 3.x EOL explicitly on
the download page once 4.0 is out. Someone landing on the download page
from a search result has no other signal that the 3.x line is done, and
"Storm 2.x has reached end of life" is exactly the kind of thing people
need to see before they start a new project on it. A short note next to
the 3.x downloads pointing at 4.0 would do it. This should wait until we
have 4.0 available though. SC 3.x will still work on Storm 3.x (we dont use
Clojure).
Best,
Richard
> Am 29.07.2026 um 16:59 schrieb Davide Polato <[email protected]>:
>
> Hi folks,
>
> I have posted a first release candidate for the Apache StormCrawler 3.7.0
> release and it is ready for testing.
>
> This release introduces a queue stream for the URLFrontier module, used to
> back off from rate-limited hosts, hold queues on Retry-After and enforce
> robots.txt Crawl-delay directives. The Selenium protocol, the CloudSearch
> indexer and the Apache HttpClient-based protocol are deprecated and will be
> removed in the next major release. It also upgrades to Apache Storm 2.8.9.
>
> Note that 3.7.0 is planned to be the final release of the 3.x line, as
> Apache Storm 2.x has reached end of life. The website changes for this
> release are on the release-3.7.0 branch of stormcrawler-site [1] - feedback
> is welcome, in particular on whether we should state the 3.x EOL explicitly
> on the site (e.g. on the download page) once 4.0 is out.
>
> Thank you to everyone who contributed to this release, including all of our
> users and the people who submitted bug reports,
> contributed code or documentation enhancements.
>
> [1] https://github.com/apache/stormcrawler-site/tree/release-3.7.0
>
> The release was made using the Apache StormCrawler release process,
> documented here:
> https://github.com/apache/stormcrawler/blob/main/RELEASING.md
>
> Source:
>
> https://dist.apache.org/repos/dist/dev/stormcrawler/stormcrawler-3.7.0-rc1
>
> Tag:
>
> https://github.com/apache/stormcrawler/releases/tag/stormcrawler-3.7.0
>
> Commit Hash:
>
> 604a97328f83073b98f1b707b38293d832fe2b81
>
> Maven Repo:
>
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1038
>
> <repositories>
> <repository>
> <id>stormcrawler-3.7.0-rc1</id>
> <name>Testing StormCrawler 3.7.0 release candidate</name>
> <url>
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1038
> </url>
> </repository>
> </repositories>
>
> Preview of website:
>
> https://stormcrawler.staged.apache.org/download/index.html
>
> Release notes:
>
> https://github.com/apache/stormcrawler/releases/tag/stormcrawler-3.7.0
>
> Reminder: The up-2-date KEYS file for signature verification can be
> found here: https://downloads.apache.org/stormcrawler/KEYS
>
> Please vote on releasing these packages as Apache StormCrawler 3.7.0
> The vote is open for at least the next 72 hours.
>
> Only votes from the StormCrawler 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.
>
> Please VOTE
>
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
>
> Thanks!
>
> Davide
