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.
1 file changed
tree: f4d22c19030574c262525b1f6d4ed40d82174f8f
  1. .github/
  2. _data/
  3. _includes/
  4. _layouts/
  5. _plugins/
  6. contribute/
  7. css/
  8. docs/
  9. download/
  10. getting-started/
  11. img/
  12. js/
  13. scripts/
  14. security/
  15. support/
  16. team/
  17. .asf.yaml
  18. .gitignore
  19. .htaccess
  20. 404.html
  21. _config-local.yml
  22. _config.yml
  23. CNAME
  24. docker-compose.yml
  25. feed.xml
  26. Gemfile
  27. index.html
  28. LICENSE
  29. NOTICE
  30. README.md
  31. robots.txt
  32. sitemap.xml
README.md

Apache StormCrawler Website

How to build?

This website is build using Jekyll. Make sure to have it available locally. To build and run server locally type ‘jekyll serve’. The site can then be accessed at localhost:4000.

Docker

You can build the website for local testing by running

docker compose up local

Deployment

This website uses the typical ASF layout. The actual website is found on the branch asf-site, any changes need to be pushed there.

You can run

docker compose up build

which will create a folder _site. This is the content, which needs to be copied after wards to the asf-site branch. If you wish to see a preview for your branch, you can use asf-staging to see a copy hosted under: https://stormcrawler.staged.apache.org/

Build with GitHub actions

The website is automatically build on a push to main and any changes are pushed to the asf-site branch. A preview is available via https://stormcrawler.staged.apache.org/ if you go to the GitHub Actions tab and trigger a manual staging deploy action.