dashorst opened a new pull request, #24: URL: https://github.com/apache/wicket-site/pull/24
Apache Infrastructure is closing down the WICKET JIRA project ([INFRA-28383](https://issues.apache.org/jira/browse/INFRA-28383)), so the site should no longer send people there to file bugs. The tracker is now [GitHub Issues](https://github.com/apache/wicket/issues). ### What changed | File | Change | | --- | --- | | `doap.rdf` | `<bug-database>` → GitHub Issues. Also feeds the project metadata on projects.apache.org. | | `help/index.md` | Both issue-tracker links; "attach the output … to the JIRA" → "to the issue". | | `_includes/security.md` | Heading "Report normal bugs in JIRA" → "… in our issue tracker". The warning *not* to file security reports in the tracker is unchanged — GitHub Issues are just as public as JIRA was. | | `contribute/patch.md` | Rewritten around GitHub Issues; **"Create a patch" section removed**. | | `contribute/release.md` | "Release the version in JIRA" → close the GitHub milestone; changelog from the milestone or generated release notes. | | `help/reportabug.md` | **Removed**, with a 301 to `/help/#reportbug`. | ### Three calls worth reviewing **Patches are gone; pull requests are the only route.** You can't attach a `.patch` file to a GitHub issue, so the `git diff --cached > /tmp/WICKET-NNNN.patch` flow had nowhere to land. The paragraph about `git-wip-us.apache.org` went with it — that host has been dead for years and only existed to explain the patch route. **`help/reportabug.md` is deleted rather than updated.** Nothing on the site has linked to it in years (the nav and `contribute/index.md` both point at `help/#reportbug`), and it described checking Wicket out of *Subversion* with Subclipse on Eclipse 3.4. One of its links was a deep-link into a 2007 comment on WICKET-497. `.htaccess` keeps the old URL alive. **The news archive is deliberately untouched.** The JIRA project stays readable, so the thousands of `WICKET-NNNN` links in 14 years of release announcements keep resolving. The two pages that tell people to search for an existing report now mention that archive alongside GitHub Issues. ### On the generated `content/` Updated by hand, not regenerated — **the site does not build from a clean checkout right now**. `_config.yml` has no `url:` key, so `jekyll-target-blank` 2.0.2 calls `URI.parse(nil)` and the build aborts. This reproduces on untouched `asf-site` and in the repo's own `.devcontainer` image, so it predates this change; `Gemfile.lock` being gitignored means gem versions drift per contributor. Each of the six regenerated pages was verified byte-for-byte against a real Jekyll build (with `url:` supplied on the command line as a workaround), so `content/` matches what the generator would produce. That build failure — and the fact that the published `feed.xml` currently serves 33 `http://0.0.0.0:4000/` URLs because `content/` was once committed from `jekyll serve` rather than `jekyll build` — is left for a separate PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
