This is an automated email from the ASF dual-hosted git repository.
dpol1 pushed a commit to branch refresh
in repository https://gitbox.apache.org/repos/asf/stormcrawler-site.git
The following commit(s) were added to refs/heads/refresh by this push:
new 62a637b Explain the release step on the contribute page
62a637b is described below
commit 62a637bcfe8f18ab7e2b51ac9ad9a168d74239fa
Author: Davide Polato <[email protected]>
AuthorDate: Mon Aug 24 12:09:30 2026 +0200
Explain the release step on the contribute page
The 04 RELEASE card only stated the three-PMC-votes rule without saying
what a release involves or what it has to do with a contributor. It now
describes the candidate and dev-list vote briefly, notes that testing a
release candidate and voting is itself a contribution, and its chip
points to the [VOTE] threads on lists.apache.org instead of the
user-facing download page.
---
contribute/index.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contribute/index.html b/contribute/index.html
index 0a3fab1..84af296 100644
--- a/contribute/index.html
+++ b/contribute/index.html
@@ -32,8 +32,8 @@ description: Questions, bug reports and pull requests are all
welcome.
<div class="vlink">
<p class="slabel">04 · RELEASE</p>
<h3>Ship it together</h3>
- <p>Releases require that at least three StormCrawler PMC members approve
the release.</p>
- <div class="chip-cluster"><a class="chip" href="{{ site.baseurl
}}/download/">DOWNLOAD →</a></div>
+ <p>Merged changes reach users through official ASF releases: a release
manager stages a candidate and the community votes on the dev list (at least
three binding PMC +1s). Testing a release candidate and voting is a
contribution too.</p>
+ <div class="chip-cluster"><a class="chip"
href="https://lists.apache.org/[email protected]:lte=3y:%5BVOTE%5D";
target="_blank" rel="noopener">RELEASE VOTES ↗</a></div>
</div>
</div>
