dev  

Messages by Thread

• [PR] Close the position tracker when the spooling reader is closed [logging-flume-rpc] via GitHub
  • Re: [PR] Close the position tracker when the spooling reader is closed [logging-flume-rpc] via GitHub
• [PR] Require the `build-result` check instead of a placeholder job [logging-flume-rpc] via GitHub
• [PR] Route GitHub notifications away from the dev list [logging-flume-rpc] via GitHub
  • Re: [PR] Route GitHub notifications away from the dev list [logging-flume-rpc] via GitHub
• [PR] Bump the maven-minor-updates group across 1 directory with 3 updates [logging-flume-rpc] via GitHub
• [D] Apache Lincense [logging-log4cxx] via GitHub
  • Re: [D] Apache Lincense [logging-log4cxx] via GitHub
  • Re: [D] Apache Lincense [logging-log4cxx] via GitHub
  • Re: [D] Apache Lincense [logging-log4cxx] via GitHub
• [PR] Bump the maven-minor-updates group with 4 updates [logging-flume-rpc] via GitHub
  • Re: [PR] Bump the maven-minor-updates group with 4 updates [logging-flume-rpc] via GitHub
  • Re: [PR] Bump the maven-minor-updates group with 4 updates [logging-flume-rpc] via GitHub
  • Re: [PR] Bump the maven-minor-updates group with 4 updates [logging-flume-rpc] via GitHub
• [PR] Flume updates [logging-flume-rpc] via GitHub
  • Re: [PR] Flume updates [logging-flume-rpc] via GitHub
  • Re: [PR] Flume updates [logging-flume-rpc] via GitHub
• [PR] Bootstrap build and release infrastructure [logging-flume-rpc] via GitHub
  • Re: [PR] Bootstrap build and release infrastructure [logging-flume-rpc] via GitHub
  • Re: [PR] Bootstrap build and release infrastructure [logging-flume-rpc] via GitHub
• [PR] Bump the maven-minor-updates group with 2 updates [logging-flume-mongodb] via GitHub
• [PR] Remove dummy `ubuntu (latest)` workflow [logging-flume-mongodb] via GitHub
  • Re: [PR] Remove dummy `ubuntu (latest)` workflow [logging-flume-mongodb] via GitHub
• [PR] Bump the github-actions-updates group with 4 updates [logging-flume-mongodb] via GitHub
• [PR] Bootstrap build and release infrastructure [logging-flume-mongodb] via GitHub
  • Re: [PR] Bootstrap build and release infrastructure [logging-flume-mongodb] via GitHub
  • Re: [PR] Bootstrap build and release infrastructure [logging-flume-mongodb] via GitHub
• [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.24.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
  • Re: [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.24.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
  • Re: [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.24.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
  • Re: [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.24.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
• [PR] handle duplicate events [logging-flume-mongodb] via GitHub
  • Re: [PR] handle duplicate events [logging-flume-mongodb] via GitHub
• [PR] Bump com.fasterxml.jackson.core:jackson-core from 2.17.0 to 2.18.8 [logging-flume-mongodb] via GitHub
• [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
  • Re: [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
  • Re: [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
  • Re: [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
  • Re: [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
  • Re: [D] [iOs] [Maui] { "Operation is not supported on this platform."} [logging-log4net] via GitHub
• [ANNOUNCE] Apache log4net 3.4.0 released Jan Friedrich
• [VOTE] Release Apache Log4net 3.4.0 Jan Friedrich
  • Re: [VOTE] Release Apache Log4net 3.4.0 Gary Gregory
  • Re: [VOTE] Release Apache Log4net 3.4.0 Stephen Webb
  • Re: [VOTE] Release Apache Log4net 3.4.0 Davyd McColl
  • Re: [VOTE] Release Apache Log4net 3.4.0 Jan Friedrich
  • [RESULT][VOTE] Release Apache Log4net 3.4.0 Jan Friedrich
  • Re: [VOTE] Release Apache Log4net 3.4.0 Jan Friedrich
  • Re: [VOTE] Release Apache Log4net 3.4.0 Gary Gregory
• Import of old releases into ATR Piotr P. Karwasz
  • Re: Import of old releases into ATR Jan Friedrich
  • Re: Import of old releases into ATR Piotr P. Karwasz
  • Re: Import of old releases into ATR Jan Friedrich
• [D] CVE-2021-45046/GHSA-7rjr-3q55-vv33 backport to 2.3.x is not reported on GHSA advisory [logging-log4j2] via GitHub
  • Re: [D] CVE-2021-45046/GHSA-7rjr-3q55-vv33 backport to 2.3.x is not reported on GHSA advisory [logging-log4j2] via GitHub
  • Re: [D] CVE-2021-45046/GHSA-7rjr-3q55-vv33 backport to 2.3.x is not reported on GHSA advisory [logging-log4j2] via GitHub
• [D] Triage of the 75 stale open PRs [logging-flume] via GitHub
• [ANNOUNCE] Apache log4cxx 1.8.0 released Stephen Webb
• [RESULT][VOTE] Release Apache Log4cxx 1.8.0 Stephen Webb
• JDK 27 Rampdown Phase is Closing / Default G1 in All Environments David Delabassee via dev
• [D] Roadmap for Apache Logging workflows [logging-log4j2] via GitHub
• [VOTE] Release Apache Log4cxx 1.8.0-RC2 Stephen Webb
  • Re: [VOTE] Release Apache Log4cxx 1.8.0-RC2 Robert Middleton
  • Re: [VOTE] Release Apache Log4cxx 1.8.0-RC2 Jan Friedrich
  • Re: [VOTE] Release Apache Log4cxx 1.8.0-RC2 Stephen Webb
• [D] Log4j 2.x audit against Oracle's Secure Coding Guidelines for Java SE [logging-log4j2] via GitHub
• [VOTE] Release Apache Log4cxx 1.8.0 Stephen Webb
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Gary Gregory
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Robert Middleton
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Robert Middleton
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Stephen Webb
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Robert Middleton
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Stephen Webb
  • Re: [VOTE] Release Apache Log4cxx 1.8.0 Stephen Webb
• [Log4cxx] new release Stephen Webb
  • Re: [Log4cxx] new release Robert Middleton
  • Re: [Log4cxx] new release Gary Gregory
  • Re: [Log4cxx] new release Robert Middleton
• [D] [Research] Performance Overhead of Tracing Data in Async Loggers: Map-Injection vs Native Fields [logging-log4j2] via GitHub
• CVE-2026-49844: Apache Log4j API: Improper serialization of non-finite floating-point values in MapMessage.asJson() Piotr Karwasz
• [ANNOUNCE] Apache Log4j `2.25.5` released Ramanathan Muthu
• [ANNOUNCE] Apache Log4j `2.26.1` released Ramanathan Muthu
• [VOTE] Release Apache Log4j `2.25.5` Ramanathan Muthu
  • Re: [VOTE] Release Apache Log4j `2.25.5` Gary Gregory
  • [DISCUSS][VOTE] Release Apache Log4j `2.25.5` Piotr P. Karwasz
  • Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.5` Gary Gregory
  • Re: [DISCUSS][VOTE] Release Apache Log4j `2.25.5` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.25.5` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.25.5` Jan Friedrich
  • Re: [VOTE] Release Apache Log4j `2.25.5` Jan Friedrich
  • Re: [VOTE] Release Apache Log4j `2.25.5` Volkan Yazıcı
  • Re: [VOTE] Release Apache Log4j `2.25.5` Ramanathan Muthu
• [D] Log4j 2.x deserialization hardening [logging-log4j2] via GitHub
• [VOTE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [VOTE] Release Apache Log4j 2.26.1 Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j 2.26.1 Jan Friedrich
  • Re: [VOTE] Release Apache Log4j 2.26.1 Gary Gregory
  • Re: [VOTE] Release Apache Log4j 2.26.1 Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j 2.26.1 Volkan Yazıcı
  • Re: [VOTE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [VOTE] Release Apache Log4j 2.26.1 Gary Gregory
  • Re: [VOTE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [VOTE] Release Apache Log4j 2.26.1 Gary Gregory
  • Re: [VOTE] Release Apache Log4j 2.26.1 Ramanathan Muthu
• [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.23.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
  • Re: [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.23.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
  • Re: [PR] Bump org.apache.thrift:libthrift from 0.14.2 to 0.23.0 in /flume-rpc-thrift [logging-flume-rpc] via GitHub
• [PR] Format with Spotless [logging-flume-rpc] via GitHub
  • Re: [PR] Format with Spotless [logging-flume-rpc] via GitHub
• [PR] version updates and code reformatting [logging-flume-rpc] via GitHub
  • Re: [PR] version updates and code reformatting [logging-flume-rpc] via GitHub
• [ANNOUNCE] Apache log4net 3.3.2 released Jan Friedrich
• [ANNOUNCE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Piotr P. Karwasz
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Volkan Yazıcı
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Piotr P. Karwasz
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Gary Gregory
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Piotr P. Karwasz
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Ramanathan Muthu
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Gary Gregory
  • Re: [ANNOUNCE] Release Apache Log4j 2.26.1 Ramanathan Muthu
• [VOTE] Release Apache Log4net 3.3.2 Jan Friedrich
  • Re: [VOTE] Release Apache Log4net 3.3.2 Davyd McColl
  • Re: [VOTE] Release Apache Log4net 3.3.2 Stephen Webb
  • Re: [VOTE] Release Apache Log4net 3.3.2 Grzegorz Dziadkiewicz
  • Re: [VOTE] Release Apache Log4net 3.3.2 Jan Friedrich
  • [RESULT][VOTE] Release Apache Log4net 3.3.2 Jan Friedrich
• [log4j] No use of `inline` in `log4j-api-kotlin`? (Discussion #4146) Volkan Yazıcı
• Re: [D] log4j 2 throws log4j 1 warnings [logging-log4j2] via GitHub
• [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
  • Re: [D] No use of `inline` in `log4j-api-kotlin`? [logging-log4j2] via GitHub
• [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
  • Re: [D] Removing `StructuredDataMessage` and all other RFC 5424 et al. [logging-log4j2] via GitHub
• [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
  • Re: [D] Threat model: how should Thread Context (MDC) keys be classified (trusted structural or untrusted content)? [logging-log4j2] via GitHub
• JDK 27 Approaches Rampdown | Final Field Mutation Warnings Heads-up David Delabassee via dev
• Archiving inactive project repositories Volkan Yazıcı
  • Re: Archiving inactive project repositories Piotr P. Karwasz
  • Re: Archiving inactive project repositories Ralph Goers
• [PR] [INFRA] Set up default rulesets for default and release branches [logging-log4j-flume] via GitHub
• Introduction: Ramanathan (ramanathan) Ramanathan Muthu
• New committer: Ramanathan Muthu Piotr P. Karwasz
  • Re: New committer: Ramanathan Muthu Ramanathan Muthu
• [ANNOUNCE] Apache Log4j `2.26.0` released Volkan Yazıcı
• [VOTE] Release Apache Log4j `2.26.0` Volkan Yazıcı
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Piotr P. Karwasz
  • Re: [VOTE] Release Apache Log4j `2.26.0` Gary Gregory
  • Re: [VOTE] Release Apache Log4j `2.26.0` Jan Friedrich
  • [RESULT][VOTE] Release Apache Log4j `2.26.0` Volkan Yazıcı
• [log4j] CI is broken, a decision needs to be made Volkan Yazıcı

• Earlier messages