Re: [VOTE] Release Apache Log4net 3.0.0

[Volkan Yazıcı]

+1

✅ Signatures
✅ Checksums
✅ Build (using Docker)
✅ Tests (using Docker)

Congratulations to the Log4net crew (in particular, to Jan and Davyd 🙇)
for their 3rd major release! 🎉 Keep up the great work! 💯



On Thu, Sep 12, 2024 at 8:54 PM Jan Friedrich  wrote:

> This is a vote to release the Apache Log4net 3.0.0.
>
> Website:
> https://logging.staged.apache.org/log4net/release/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> GitHub release (pre-release):
> https://github.com/apache/logging-log4net/releases/tag/rc/3.0.0-rc1
> Commit: 42ba791745ceb7ff922d828c6c5572ed918df84b
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net
> Signing key: 0x7D24496A230E29D6349A99EF583E491578F02D5D
>
>
> Please download, test, and cast your votes on this mailing list.
>
> How to run the unit tests?
> - install docker (if you haven't already)
>   - https://docs.docker.com/engine/install/
> - in logging/log4net run
>   - `docker build -t log4net-builder .`
>   - `docker run -it log4net-builder`
> - this will
>   - install all dependencies in the container
>   - build src/log4net.sln
>   - inside the container run
> - `dotnet test /logging-log4net/src/log4net.sln`
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because ...
>
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
>
>

[log4j] Spring Boot 3.4.0 will introduce structured logging

[Volkan Yazıcı]

See the related release note
.
With this change, Spring Boot will effectively be providing an
implementation-agnostic logging system abstraction featuring:

   - Level support
   - Pattern layout support
   - Structured (i.e., JSON) layout support (New!)

Note that many modern SOA deployment solutions
 expect application logs to
be written to the console, which renders the need for specialized appenders
obsolete. Given this, if I may say, Spring Boot's logging abstraction
pretty much makes the need to employ/configure a logging system obsolete –
Spring Boot aims to cover 90% of logging-related use cases with its
in-house abstractions. I can imagine a majority of its users will be able
to develop and deploy to production without any `log4j2.xml`,
`logback.xml`, or `logging.properties` configurations.

Re: [log4j] Spring Boot 3.4.0 will introduce structured logging

[Ralph Goers]

While this is nice I don’t think it will result in killing off logging 
frameworks. While it supports the MDC it does not support structured messages.

At the moment I don’t think it will support custom ContextDataProviders, but 
that should come for free when I can get log4j-context-data completed.

It also presumes you want all your ThreadContext keys included. We pass the 
OAuth token in the ThreadContextMap and would not what that included as it is 
huge and provides no value.

At the moment to perform any customization you have to write your own 
StructuredLogFormatter. The example they provide isn’t going to perform 
particularly well which makes me wonder what the default implementation does.

Ralph

> On Sep 13, 2024, at 2:07 AM, Volkan Yazıcı  wrote:
> 
> See the related release note
> .
> With this change, Spring Boot will effectively be providing an
> implementation-agnostic logging system abstraction featuring:
> 
>   - Level support
>   - Pattern layout support
>   - Structured (i.e., JSON) layout support (New!)
> 
> Note that many modern SOA deployment solutions
>  expect application logs to
> be written to the console, which renders the need for specialized appenders
> obsolete. Given this, if I may say, Spring Boot's logging abstraction
> pretty much makes the need to employ/configure a logging system obsolete –
> Spring Boot aims to cover 90% of logging-related use cases with its
> in-house abstractions. I can imagine a majority of its users will be able
> to develop and deploy to production without any `log4j2.xml`,
> `logback.xml`, or `logging.properties` configurations.

Re: [log4j] Spring Boot 3.4.0 will introduce structured logging

[Matt Sicker]

Let’s not conflate Spring Boot with Java. Besides the proliferation of numerous 
competing frameworks, there are plenty of use cases for smaller applications, 
too.

> On Sep 13, 2024, at 11:48, Ralph Goers  wrote:
> 
> While this is nice I don’t think it will result in killing off logging 
> frameworks. While it supports the MDC it does not support structured messages.
> 
> At the moment I don’t think it will support custom ContextDataProviders, but 
> that should come for free when I can get log4j-context-data completed.
> 
> It also presumes you want all your ThreadContext keys included. We pass the 
> OAuth token in the ThreadContextMap and would not what that included as it is 
> huge and provides no value.
> 
> At the moment to perform any customization you have to write your own 
> StructuredLogFormatter. The example they provide isn’t going to perform 
> particularly well which makes me wonder what the default implementation does.
> 
> Ralph
> 
>> On Sep 13, 2024, at 2:07 AM, Volkan Yazıcı  wrote:
>> 
>> See the related release note
>> .
>> With this change, Spring Boot will effectively be providing an
>> implementation-agnostic logging system abstraction featuring:
>> 
>>  - Level support
>>  - Pattern layout support
>>  - Structured (i.e., JSON) layout support (New!)
>> 
>> Note that many modern SOA deployment solutions
>>  expect application logs to
>> be written to the console, which renders the need for specialized appenders
>> obsolete. Given this, if I may say, Spring Boot's logging abstraction
>> pretty much makes the need to employ/configure a logging system obsolete –
>> Spring Boot aims to cover 90% of logging-related use cases with its
>> in-house abstractions. I can imagine a majority of its users will be able
>> to develop and deploy to production without any `log4j2.xml`,
>> `logback.xml`, or `logging.properties` configurations.
>