I would like to have the following completed before we release 2.7: - https://issues.apache.org/jira/browse/LOG4J2-1530 - https://issues.apache.org/jira/browse/LOG4J2-1528 - https://issues.apache.org/jira/browse/LOG4J2-1512 - https://issues.apache.org/jira/browse/LOG4J2-1181 - https://issues.apache.org/jira/browse/LOG4J2-1010 - https://issues.apache.org/jira/browse/LOG4J2-63
I am waiting for review of theses branches: LOG4J-1181, LOG4J2-1512 and LOG4J2-1528. On Tue, Aug 23, 2016 at 2:55 AM, Matt Sicker <[email protected]> wrote: > I'd like to finish the documentation for the AsyncAppender updates. I > believe we also have a few outstanding branches now that could make it into > 2.7. > > On 22 August 2016 at 19:39, Ralph Goers <[email protected]> > wrote: > >> I’m sure I have stuff I want to do. It just isn’t going to get done this >> week. The soonest I could target doing a release would be labor day >> weekend. But I expect I will probably spend most of that addressing issues >> I’ve been trying to get to. >> >> Ralph >> >> On Aug 22, 2016, at 5:32 PM, Gary Gregory <[email protected]> wrote: >> >> Wow, we've already accumulated 35 items in changes.xml since release >> 2.6.2 on July 5! >> >> I'm not sure if that is good or bad ;-) but we should think about what we >> want to complete for the next release. >> >> Thoughts? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> >> >> > > > -- > Matt Sicker <[email protected]> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] 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.
