I'll review in the morning (EST).
Gary
On Sat, Dec 11, 2021, 23:02 Matt Sicker wrote:
> If possible, let’s try to get this vote done over the next 24 hours.
>
> Matt Sicker
>
> > On Dec 11, 2021, at 21:48, Matt Sicker wrote:
> >
> > This is a vote to release Log4j 2.15.1, the next version of
Or less. While it is not an essential release I believe it will be appreciated.
Ralph
> On Dec 11, 2021, at 9:01 PM, Matt Sicker wrote:
>
> If possible, let’s try to get this vote done over the next 24 hours.
>
> Matt Sicker
>
>> On Dec 11, 2021, at 21:48, Matt Sicker wrote:
>>
>> This is
If possible, let’s try to get this vote done over the next 24 hours.
Matt Sicker
> On Dec 11, 2021, at 21:48, Matt Sicker wrote:
>
> This is a vote to release Log4j 2.15.1, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
This is a vote to release Log4j 2.15.1, the next version of the Log4j 2 project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All votes are
welco
Agreed. I didn’t realize this feature existed like that until recently, and
it’s not worth salvaging.
Matt Sicker
> On Dec 11, 2021, at 09:25, Ralph Goers wrote:
>
> I agree. Remove it from master.
>
> Ralph
>
>> On Dec 11, 2021, at 7:42 AM, Carter Kozak wrote:
>>
>> Agreed that the featu
I agree. Remove it from master.
Ralph
> On Dec 11, 2021, at 7:42 AM, Carter Kozak wrote:
>
> Agreed that the feature should be purged entirely. I turned it off by default
> with no global enablement on release-2.x (shipped in 2.15).
>
> -ck
>
>> On Dec 11, 2021, at 09:13, Mikael Ståldal wro
Agreed that the feature should be purged entirely. I turned it off by default
with no global enablement on release-2.x (shipped in 2.15).
-ck
> On Dec 11, 2021, at 09:13, Mikael Ståldal wrote:
>
> I would say that log messages and log message parameter are as much (or as
> little) controlled
I would say that log messages and log message parameter are as much (or
as little) controlled by the application. I don't think it make sense to
see them differently from a security perspective.
Just as some code might do:
logger.info("some message {}", userInput);
Other code might do:
log
Guten Tag Robert Middleton,
am Montag, 29. November 2021 um 04:53 schrieben Sie:
> At this point, I believe that I have converted all of the important
> classes to be ABI-stable.[...]
Not that it's too representative, but things properly build and test
for my pretty current VS 17.02 as well.
> A
