Log4j 2.3.x and 2.12.x don’t need votes. We declared that we were no longer
supporting Java 6 and then Java 7 and that those would be the last releases to
do so. We made an exception for Log4Shell and created patches for both since
the security exposure was so bad. Those release lines are clearl
Hi all,
Looking at our releases, as the appear on `projects.apache.org`[1], I
think that it is about time to clean up `downloads.apache.org`. I would
propose to:
1. Formally vote on the end-of-life of the Apache Extras for Apache
log4j[2] and Apache log4php[3] projects.
2. Formally vote on
Hi Volkan,
On 13.11.2024 16:54, Volkan Yazıcı wrote:
On Wed, Nov 13, 2024 at 4:38 PM Piotr P. Karwasz
wrote:
6. Currently we place all sub-projects of Log4j directly in the
`logging` folder, but `archive.apache.org`[6] shows that it wasn't
always this way. For example `log4j-scala` used to be
On Wed, Nov 13, 2024 at 4:38 PM Piotr P. Karwasz
wrote:
> 6. Currently we place all sub-projects of Log4j directly in the
> `logging` folder, but `archive.apache.org`[6] shows that it wasn't
> always this way. For example `log4j-scala` used to be in `log4j/scala`.
> Which convention should we use
