I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I have a branch out for review.
On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <boa...@gmail.com> wrote: > I'm working on getting the Log4j Scala repo set up independently from the > main Log4j repo (and doing Log4j Boot on the side; this will be released > independently, so don't worry about this blocking anything) and doing some > general site cleanups and whatnot. For 2.8, the other non-core modules will > most likely remain where they are and the Log4j Scala API repo gets to be > our first foray into the separated repos space. > > Feature-wise, are there any other things we'd like to complete before > cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the > pain points of migrating config formats being brought up again, so it would > be great to get our Log4j 1 config support in this release, but that > depends on timing, too (we could always RERO and add it to the next release > if nobody has time to finish that feature). > > -- > 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.
