+1 Works for me.
On Sun, Apr 2, 2017 at 11:08 PM, Matt Sicker <boa...@gmail.com> wrote: > This is a vote to release Log4j 2.8.2. Please download, test, and cast > your votes on this mailing list. > > [] +1, release the artifacts > > [] -1, don't release because... > > The vote will remain open for 72 hours at least. All votes are welcome, > and we encourage everyone to test the release, but only Logging PMC votes > are counted towards the "official" vote count. As always, at least 3 +1s > and more +1s than -1s are required. > > Changes in this version include: > > <https://github.com/apache/logging-log4j2/blob/master/RELEASE-NOTES.md#new-features>New > Features > > - LOG4J2-1863 <https://issues.apache.org/jira/browse/LOG4J2-1863>: Add > support for filtering input in TcpSocketServer and UdpSocketServer. > - LOG4J2-1848 <https://issues.apache.org/jira/browse/LOG4J2-1848>: Add > JSON encoding support to EncodingPatternConverter %encode{}. > - LOG4J2-1843 <https://issues.apache.org/jira/browse/LOG4J2-1843>: Add > support for appending common suffix to each line of throwable stack trace. > Thanks to Zilong Song. > - LOG4J2-1838 <https://issues.apache.org/jira/browse/LOG4J2-1838>: Add > support for appending common suffix to each line of extended and root > throwable stack trace. Thanks to Zilong Song. > > > <https://github.com/apache/logging-log4j2/blob/master/RELEASE-NOTES.md#fixed-bugs>Fixed > Bugs > > - LOG4J2-1861 <https://issues.apache.org/jira/browse/LOG4J2-1861>: Fix > JavaDoc on org.apache.logging.log4j.ThreadContext about inheritance. > - LOG4J2-1862 <https://issues.apache.org/jira/browse/LOG4J2-1862>: Fix > JavaDoc about @Order and OrderComparator ordering. Thanks to wangyuntao. > - LOG4J2-1849 <https://issues.apache.org/jira/browse/LOG4J2-1849>: > Fixed daylight savings time issue with FixedDateFormat. > - LOG4J2-1850 <https://issues.apache.org/jira/browse/LOG4J2-1850>: Fix > CassandraRule and unit tests on Windows. Thanks to Ludovic Hochet. > - LOG4J2-1840 <https://issues.apache.org/jira/browse/LOG4J2-1840>: Fix > typo in %replace converter documentation. Thanks to Pradeep Balasundaram. > - LOG4J2-1846 <https://issues.apache.org/jira/browse/LOG4J2-1846>: > Handle when LogEvent.getLoggerName() returns null in > LoggerNameLevelRewritePolicy. > - LOG4J2-1845 <https://issues.apache.org/jira/browse/LOG4J2-1845>: > Handle when LogEvent.getLoggerName() returns null in KafkaAppender. > - LOG4J2-1853 <https://issues.apache.org/jira/browse/LOG4J2-1853>: The > default value of RandomAccessFileAppender.Builder append field is > wrong. Thanks to wangyuntao. > - LOG4J2-1835 <https://issues.apache.org/jira/browse/LOG4J2-1835>: Fix > documentation about the licensing for JeroMQ. > - LOG4J2-1836 <https://issues.apache.org/jira/browse/LOG4J2-1836>: > Update the API version to 2.6.0. > - LOG4J2-1831 <https://issues.apache.org/jira/browse/LOG4J2-1831>: > NullPointerException in HtmlLayout. Thanks to Edward Serebrinskiy. > - LOG4J2-1820 <https://issues.apache.org/jira/browse/LOG4J2-1820>: > Log4j 2.8 can lose exceptions when a security manager is present. Thanks to > Jason Tedor. > > > <https://github.com/apache/logging-log4j2/blob/master/RELEASE-NOTES.md#changes> > Changes > > - LOG4J2-1827 <https://issues.apache.org/jira/browse/LOG4J2-1827>: > Move integration tests to their own module to speed up build. > - LOG4J2-1856 <https://issues.apache.org/jira/browse/LOG4J2-1856>: > Update Jackson from 2.8.6 to 2.8.7. > > Tag: log4j-2.8.2-rc1 > > Web site: https://rgoers.github.io/log4j2-site/ > > Artifacts: https://repository.apache.org/content/ > repositories/orgapachelogging-1026/ > > You can download all the artifacts via the command line: > > wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate > https://repository.apache.org/content/repositories/orgapachelogging-1026/ > > -- > Matt Sicker <boa...@gmail.com> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.