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
On Tue, Feb 6, 2024 at 5:06 PM Piotr P. Karwasz <piotr.karw...@gmail.com>
wrote:
> Hi all,
>
> The current `asf-site` branch of the `logging-log4j-site` repo has
> about 450k files, which makes it very hard to work on it.
>
> Most of those are websites of old releases that I doubt anybody
> (except search engines) visits. Those websites also pollute search
> engine results: several times I found the page of an old release
> better ranked that the current version.
>
> Therefore I created a new branch `clean-log4j`[1] (which is published
> as [2]) that contains only these directories:
>
> * 1.x: last 1.x release.
> * 2.3: last 2.3 release. Although not strictly necessary, I thought
> that people stuck with Java 6 will appreciate a website without all
> the features from newer releases.
> * 2.12: last 2.12 release.
> * 2.x: latest 2.x release.
> * 3.x: latest 3.x release.
> * extras: last Apache Log4j Extras release.
>
> and the XML schemata for our changelog format (although they should be
> moved to `/xml/ns/changelog`).
>
> All the `log4j-<version>` and similar directories are redirected
> (permanent 301 redirect) to one of the remaining one: e.g.
> `log4j-2.0.1` is redirected to `2.3`, `log4j-2.4` is redirected to
> `2.12`, while `2.13.0` (sic!) is redirected to `2.x`.
>
> For those that like to go down memory lane, the branch contains 65
> commits for each one of our releases.
>
> What do you think about replacing `asf-site` with this branch?
>
> Piotr
>
> [1] https://github.com/apache/logging-log4j-site/tree/clean-staging
> [2] https://logging-clean.staged.apache.org/log4j
>
