Hi all,
On Mon, 19 Feb 2024 at 10:34, Volkan Yazıcı <vol...@yazi.ci> wrote:
>
> If there are no objections, after Log4j `2.23.0` and `3.0.0-beta2`
> releases, I want to proceed with replacing the contents of
> `asf-{site,staging}` branches with `clean-staging`. Effectively, this
> operation has the following outcomes:
>
> - The `logging-log4j-site` repository will contain only following files:
> - `1.x`
> - `2.12.x`
> - `2.3.x`
> - `2.x`
> - `3.x`
> - `.asf.yaml`
> - `changelog-*.xsd`
> - `extras`
> - `.htaccess`
> - `.htaccess` will take care of redirections for backward compatibility
I replaced `asf-site` with `asf-staging`. The results for
Log4j-related queries in search engines should slowly converge to one
of `2.x`, `2.3.x` and `2.12.x`.
There is a further simplification possible: since Oracle's extended
support for Java 7 has expired in July 2022, shouldn't we also
redirect the `2.3.x` and `2.12.x` websites to `2.x`?
Piotr
