dashorst opened a new pull request, #25:
URL: https://github.com/apache/wicket-site/pull/25

   Follows up on the PMC announcement on announce@ and users@: from Wicket 
11.0.0 onwards we move to time-based releases, a major release every three 
months with every fourth one an LTS.
   
   **News item** `2026/_posts/2026-09-11-release-cadence.md` — the 
announcement, with the schedule 11 → 14, the reasons (slowdown, the CVE load 
multiplied across four supported branches, LLM-scale cleanups versus semver), 
and the stability promise. It also answers the follow-up question from users@ 
("is a feature released in one quarter supported for only three months?"): the 
support window applies to the release line, not to individual features. 
Features are developed on `main` and carry over into every following release; 
what the window decides is which release lines receive fixes — the current LTS 
and the current quarterly release, at most two at a time.
   
   **Download page** `start/download.md` — a Release Policy section rather than 
only a link to the news item, since that page is where people land when they 
need to pick a version. The Supported Versions table above it still describes 
today's situation; the new schedule only takes effect when 11.0.0 is released. 
The status of 8.x and 9.x now reads "one final release, then end of life".
   
   `content/` is regenerated (news item, download page, news-archive sidebars, 
`atom.xml`, `feed.xml`, homepage, learn index) — the same shape as the commit 
for 8.19.0/9.24.0/10.11.0.
   
   Two things to check before merging:
   
   - The announcement says 8.x and 9.x each get one more release, which is what 
both texts say here. 8.19.0 and 9.24.0 shipped on 30 August — if those *were* 
the final ones, the wording needs to change to past tense.
   - "Wicket 14 supported until Wicket 18" is derived from "every fourth major 
release is an LTS". The announcement does not state it literally.
   
   Unrelated, but worth a separate PR: `jekyll build` fails on `asf-site` as it 
stands. `_config.yml` has no `url:`, and jekyll-target-blank 2.0.2 calls 
`URI.parse(@site_url)` on nil. I built with an override `url: ""`, which 
reproduces the committed output byte for byte; setting it to 
`https://wicket.apache.org` is *not* a drop-in fix, because then every link to 
our own host stops being external and loses `target="_blank" rel="noopener 
noreferrer"`. `content/css/style.css` also differs under a newer sass 
(percentage `rgb()` notation); that churn is left out of this PR.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to