Re: Import of old releases into ATR

Jan Friedrich <[email protected]>
Newsgroups gmane.comp.jakarta.log4j.devel
Message-ID <[email protected]>
Hi Piotr, 

thanks for handling this. 
log4net retires old major versions when the first new major is released. 

Jan

On August 12, 2026 1:31:01 PM GMT+02:00, "Piotr P. Karwasz" <[email protected]> wrote:
>Hello all,
>
>As some of you might have noticed, Apache Trusted Releases has
>retroactively created releases for all the files in archive.apache.org,
>using a modified version of the heuristic from projects.apache.org:
>
>https://release-catalog-test.apache.org/logging/index.html
>
>Since the heuristic is based on keywords and "log4j" appears often, some
>artifacts are misclassified (e.g., Log4j Scala releases are classified
>as Log4j).
>
>I reached out to Tooling to get database dumps (as CSV files) for the
>part related to Logging Services, and I've corrected them here:
>
>https://gist.github.com/ppkarwasz/27dd55b79bde688cb5d83563c305febf
>
>The gist includes a changes.md explaining what was modified and why. All
>the files in the following folder should have been classified:
>
>incubator/{flume,log4cxx,log4net,log4php}
>jakarta/log4j
>flume/
>logging/
>
>Could you review these files before I send them back to Tooling?
>
>One outstanding question:
>- When were the Log4net 1.x and 2.x final releases retired: at the same
>time as the first release of the next series, or shortly after?
>
>Piotr
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.