Re: Removal of 2.3.x and 2.12.x websites (was: Clean site repo)

2024-03-04 Thread Volkan Yazıcı
I suggest simply adding a giant banner[1] warning users and compiling a robots.txt for SSO. [1] I believe we can do this by simply editing a couple of CSS files, instead of modifying every single HTML. On Mon, Mar 4,

Re: [VOTE] Release Apache Log4net 2.0.16

2024-03-04 Thread Ralph Goers
+1 Verified signatures Verified hashes Verified License and Notice files. Note - the copyright year should be the first year the code was created. You can update it to include “-(currentYear}” but that is not strictly necessary. Ralph > On Mar 4, 2024, at 10:48 AM, Jan Friedrich wrote: > >

Re: Removal of 2.3.x and 2.12.x websites (was: Clean site repo)

2024-03-04 Thread Piotr P. Karwasz
Hi Ralph, On Mon, 4 Mar 2024 at 20:53, Ralph Goers wrote: > > On Mar 4, 2024, at 6:24 AM, Piotr P. Karwasz > > wrote: > > > > 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

Re: Removal of 2.3.x and 2.12.x websites (was: Clean site repo)

2024-03-04 Thread Ralph Goers
> On Mar 4, 2024, at 6:24 AM, Piotr P. Karwasz wrote: > > 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`? Why would we do that? I mean we don’t officiall

Re: [VOTE] Release Apache Log4net 2.0.16

2024-03-04 Thread Jan Friedrich
+1 Unit tests on my machine were successful. We integrated the new version into our test environment and all manual tests were successful. Jan > +1 > Verified signatures. > Verified hashes. > `NOTICE` contains 2022 as the copyright year, but I don't find it a > blocker. (I have fixed it in `m

Removal of 2.3.x and 2.12.x websites (was: Clean site repo)

2024-03-04 Thread Piotr P. Karwasz
Hi all, On Mon, 19 Feb 2024 at 10:34, Volkan Yazıcı 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 outc

Re: [VOTE] Release Apache Log4net 2.0.16

2024-03-04 Thread Volkan Yazıcı
+1 Verified signatures. Verified hashes. `NOTICE` contains 2022 as the copyright year, but I don't find it a blocker. (I have fixed it in `master`.) On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: > Hi all > > > This is the vote to release Apache log4net version 2.0.16 > > > Website: > http