Here are my votes: > On Oct 30, 2023, at 1:44 AM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > This is a vote to deprecate the following `2.x` modules and features > and remove them from the `3.x` release: > > * `log4j-cassandra`: +1 > * CouchDB appender: +1 > * `log4j-docker` -1 - Still useful and supportable > * GELF appender: +1 - JsonTemplateLayout replaces this > * Kafka appender: +1 (I have mixed feelings about this. It would obviously be useful but the version we support is ancient and doesn’t support many things one would want) > * `log4j-kubernetes`: -1 Still useful and supportable > * JeroMQ appender: +0 I’ve never used JeroMQ. > * JNDI-related features: -1 Unfortunately, JEE users require this. > * `log4j-jpa`: +0 I’ve never cared about logging to an RDBMS. > * Jackson based layouts (JsonLayout, XmlLayout, YamlLayout) +0 (We have no replacement for logging to XML or Yaml although I have no idea why one would want tot). > * `log4j-mongodb3`: +1 > * `log4j-spring-boot`: +1 (Spring provides this in Spring 3 and users or that should use Log4j 3.x) > * Java EE SMTP appender: +0 > * Jakarta EE SMTP appender: +0 > * `log4j-taglib`: +0 (I never understood the purpose of this).
Ralph > > Please cast votes for each module/feature separately on this mailing list: > > [ ] +1, drop the artifact/module, > [ ] +/-0 > [ ] -1, keep the artifact/module, because... > > This vote is open for 168 hours (i.e. one week) and each deprecation > will pass unless getting a net negative vote count. All votes are > welcome, but only the Logging Services PMC votes are officially > counted. > > Piotr
