Fwd: MODERATE for annou...@apache.org

[Private List Moderation]

For future reference, the download page does not meet requirements. 
https://www.apache.org/dev/release-distribution#download-links

SHA1 is no longer considered a reliable checksum. Please convert to use SHA256 
and/or SHA512 for future releases. The requirements are SHOULD NOT for SHA1 
solely because of downstream scripts that may need to be adapted.

There is no need to go back to earlier releases and add/replace checksums. But 
releases going forward need to change. 

Regards,

Craig

> Begin forwarded message:
> 
> From: announce-reject-1561868463.6757.aijfalmmkjblpchhn...@apache.org
> Subject: MODERATE for annou...@apache.org
> Date: June 29, 2019 at 9:21:03 PM PDT
> To: Recipient list not shown: ;
> Cc: 
> announce-allow-tc.1561868463.dojocliaafkhphoiapbi-rgoers=apache@apache.org
> Reply-To: announce-accept-1561868463.6757.aijfalmmkjblpchhn...@apache.org
> 
> 
> To approve:
>   announce-accept-1561868463.6757.aijfalmmkjblpchhn...@apache.org
> To reject:
>   announce-reject-1561868463.6757.aijfalmmkjblpchhn...@apache.org
> To give a reason to reject:
> %%% Start comment
> %%% End comment
> 
> 
> From: Ralph Goers 
> Subject: [ANNOUNCEMENT] Apache Log4j 2.12.0 released
> Date: June 29, 2019 at 9:21:00 PM PDT
> To: annou...@apache.org
> Reply-To: rgo...@apache.org
> 
> 
> The Apache Log4j 2 team is pleased to announce the Log4j 2.12.0 release!
> 
> Apache Log4j is a well known framework for logging application behavior. 
> Log4j 2 is an upgrade to Log4j that provides significant improvements over 
> its predecessor, Log4j 1.x, and provides many other modern features such as 
> support for Markers, lambda expressions for lazy logging, property 
> substitution using Lookups, multiple patterns on a PatternLayout and 
> asynchronous Loggers. Another notable Log4j 2 feature is the ability to be 
> "garbage-free" (avoid allocating temporary objects) while logging. In 
> addition, Log4j 2 will not lose events while reconfiguring.
> 
> The artifacts may be downloaded 
> fromhttps://logging.apache.org/log4j/2.x/download.html.
> 
> This release contains bugfixes and minor enhancements.
> 
> Due to a break in compatibility in the SLF4J binding, Log4j now ships with 
> two versions of the SLF4J to Log4j adapters. log4j-slf4j-impl should be used 
> with SLF4J 1.7.x and earlier and log4j-slf4j18-impl should be used with SLF4J 
> 1.8.x and later.
> 
> New features include support for reconnfiguration of Log4j configuraton files 
> accessed via HTTP(s) and Spring Cloud Config specifically, a new Docker 
> Lookup for obtaining information about the current Docker container, new 
> reconfiguration methods added to the Configurator class, the ability to pad 
> integers with leading zeros in filenames generated by the rolling file 
> appenders, and allowing the TCP SocketAppender to connect to mulitple ip 
> addresses when they are returned from DNS.
> 
> More details on the new features and fixes are itemized below.
> 
> Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they 
> no longer have the "timeMillis" attribute and instead have an "Instant" 
> element with "epochSecond" and "nanoOfSecond" attributes.
> 
> The Log4j 2.12.0 API, as well as many core components, maintains binary 
> compatibility with previous releases.
> 
> GA Release 2.12.0
> 
> Changes in this version include:
> 
> New Features
> 
> • LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. 
> Thanks to hupfdule.
> • LOG4J2-2427: Add filter that will match events when no marker is present. 
> Thanks to Rimaljit Kaur.
> • LOG4J2-2406: Add reconfiguration methods to Configurator.
> • LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and Spring 
> Cloud Configuration.
> • LOG4J2-2586: TCP Appender should support a host name resolving to multiple 
> IP addresses.
> • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind 
> Sahare, Patrice Ferrot.
> • LOG4J2-2598: GZIP compression on rollover supports configurable compression 
> levels. Thanks to Carter Kozak.
> • LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and 
> "Discard" are case insensitive to avoid confusion.
> • LOG4J2-2634: Add and use method 
> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler 
> subclasses.
> Fixed Bugs
> 
> • LOG4J2-2547: RollingRandomAccessFileAppender error message referenced 
> incorrect class name.
> • LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was 
> removed in 2.8.2.
> • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> • LOG4J2-2636: RFC5424Layout was not properly setting default Structured 
> Element id for the MDC
> • LOG4J2-1143: Lookups were not found if the plugin key was not lowercase. 
> Thanks to Pascal Heinrich.
> • LOG4J2-1852: Locate plugins within a Jar using a URL Connection. Thanks to 
> Tanner Altares.
> • LOG4J2-2610: Explicitly set file creation time.
> • LOG4J2-2561: JEP223 version detection fix

Re: MODERATE for annou...@apache.org

[Ralph Goers]

Craig,

Thanks for catching that. The artifacts are actually check-summed with SHA512. 
The links on the web page are just bad. I will fix that asap.

Ralph

> On Jun 30, 2019, at 7:23 AM, Private List Moderation  
> wrote:
> 
> For future reference, the download page does not meet requirements. 
> https://www.apache.org/dev/release-distribution#download-links
> 
> SHA1 is no longer considered a reliable checksum. Please convert to use 
> SHA256 and/or SHA512 for future releases. The requirements are SHOULD NOT for 
> SHA1 solely because of downstream scripts that may need to be adapted.
> 
> There is no need to go back to earlier releases and add/replace checksums. 
> But releases going forward need to change. 
> 
> Regards,
> 
> Craig
> 
>> Begin forwarded message:
>> 
>> From: announce-reject-1561868463.6757.aijfalmmkjblpchhn...@apache.org
>> Subject: MODERATE for annou...@apache.org
>> Date: June 29, 2019 at 9:21:03 PM PDT
>> To: Recipient list not shown: ;
>> Cc: 
>> announce-allow-tc.1561868463.dojocliaafkhphoiapbi-rgoers=apache@apache.org
>> Reply-To: announce-accept-1561868463.6757.aijfalmmkjblpchhn...@apache.org
>> 
>> 
>> To approve:
>>  announce-accept-1561868463.6757.aijfalmmkjblpchhn...@apache.org
>> To reject:
>>  announce-reject-1561868463.6757.aijfalmmkjblpchhn...@apache.org
>> To give a reason to reject:
>> %%% Start comment
>> %%% End comment
>> 
>> 
>> From: Ralph Goers 
>> Subject: [ANNOUNCEMENT] Apache Log4j 2.12.0 released
>> Date: June 29, 2019 at 9:21:00 PM PDT
>> To: annou...@apache.org
>> Reply-To: rgo...@apache.org
>> 
>> 
>> The Apache Log4j 2 team is pleased to announce the Log4j 2.12.0 release!
>> 
>> Apache Log4j is a well known framework for logging application behavior. 
>> Log4j 2 is an upgrade to Log4j that provides significant improvements over 
>> its predecessor, Log4j 1.x, and provides many other modern features such as 
>> support for Markers, lambda expressions for lazy logging, property 
>> substitution using Lookups, multiple patterns on a PatternLayout and 
>> asynchronous Loggers. Another notable Log4j 2 feature is the ability to be 
>> "garbage-free" (avoid allocating temporary objects) while logging. In 
>> addition, Log4j 2 will not lose events while reconfiguring.
>> 
>> The artifacts may be downloaded 
>> fromhttps://logging.apache.org/log4j/2.x/download.html.
>> 
>> This release contains bugfixes and minor enhancements.
>> 
>> Due to a break in compatibility in the SLF4J binding, Log4j now ships with 
>> two versions of the SLF4J to Log4j adapters. log4j-slf4j-impl should be used 
>> with SLF4J 1.7.x and earlier and log4j-slf4j18-impl should be used with 
>> SLF4J 1.8.x and later.
>> 
>> New features include support for reconnfiguration of Log4j configuraton 
>> files accessed via HTTP(s) and Spring Cloud Config specifically, a new 
>> Docker Lookup for obtaining information about the current Docker container, 
>> new reconfiguration methods added to the Configurator class, the ability to 
>> pad integers with leading zeros in filenames generated by the rolling file 
>> appenders, and allowing the TCP SocketAppender to connect to mulitple ip 
>> addresses when they are returned from DNS.
>> 
>> More details on the new features and fixes are itemized below.
>> 
>> Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they 
>> no longer have the "timeMillis" attribute and instead have an "Instant" 
>> element with "epochSecond" and "nanoOfSecond" attributes.
>> 
>> The Log4j 2.12.0 API, as well as many core components, maintains binary 
>> compatibility with previous releases.
>> 
>> GA Release 2.12.0
>> 
>> Changes in this version include:
>> 
>> New Features
>> 
>> • LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. 
>> Thanks to hupfdule.
>> • LOG4J2-2427: Add filter that will match events when no marker is present. 
>> Thanks to Rimaljit Kaur.
>> • LOG4J2-2406: Add reconfiguration methods to Configurator.
>> • LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and 
>> Spring Cloud Configuration.
>> • LOG4J2-2586: TCP Appender should support a host name resolving to multiple 
>> IP addresses.
>> • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind 
>> Sahare, Patrice Ferrot.
>> • LOG4J2-2598: GZIP compression on rollover supports configurable 
>> compression levels. Thanks to Carter Kozak.
>> • LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and 
>> "Discard" are case insensitive to avoid confusion.
>> • LOG4J2-2634: Add and use method 
>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler 
>> subclasses.
>> Fixed Bugs
>> 
>> • LOG4J2-2547: RollingRandomAccessFileAppender error message referenced 
>> incorrect class name.
>> • LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was 
>> removed in 2.8.2.
>> • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>> • LOG4J2-2636: RFC5424Layout was not properly setti

Re: Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

[Carter Kozak]

Hi Folks,

I've registered to attend ApacheCon Vegas, hoping to see you there!

-ck

On Sun, May 19, 2019, at 14:38, Matt Sicker wrote:
> Hello everyone! This year, I know of at least two submissions to
> ApacheCon Las Vegas that are related to Log4j. While the schedule
> hasn't been confirmed or posted yet, TAC has opened up applications
> now to be able to go to ApacheCon. If you'd love to come to ApacheCon
> this year but are financially unable to afford doing so, please take a
> look into the Apache TAC for financial assistance in getting you out
> to ApacheCon! I'd love to see everyone in person this year (I'm hoping
> to go this time).
> 
> -- Forwarded message -
> From: Gavin McDonald 
> Date: Fri, 17 May 2019 at 01:30
> Subject: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.
> To: 
> 
> 
> Hi PMCs!
> 
> Please redistribute the below to your user and dev lists, feel free to
> also use social media to spread the word. Thanks!
> 
> Gav... TAC Team
> 
> ---
> 
> The Travel Assistance Committee (TAC) are pleased to announce that
> travel assistance applications for ApacheCon NA 2019 are now open!
> 
> We will be supporting ApacheCon NA Las Vegas, Nevada on 9th - 12th
> September 2019
> 
> TAC exists to help those that would like to attend ApacheCon events,
> but are unable to do so for financial reasons.
> For more info on this years applications and qualifying criteria,
> please visit the TAC website at < http://www.apache.org/travel/
>  >. Applications opened today and will
> close around the 21st June.
> 
> Important: Applications close on June 21st, 2019. Applicants have
> until the closing date above to submit their applications (which
> should contain as much supporting material as required to efficiently
> and accurately process their request), this will enable TAC to
> announce successful awards shortly afterwards.
> 
> As usual, TAC expects to deal with a range of applications from a
> diverse range of backgrounds. We therefore encourage (as always)
> anyone thinking about sending in an application to do so ASAP.
> We look forward to greeting many of you in Las Vegas!
> 
> Kind Regards,
> Gavin - (On behalf of the Travel Assistance Committee)
> 
> 
> -- 
> Matt Sicker 
>