To be clear, I am not planning on doing a 3.0.0 release this weekend. But when we do I would like there to be a good story as to why one would want to move up.
Ralph > On Jun 27, 2018, at 8:19 AM, Matt Sicker <[email protected]> wrote: > > It'd be nice to clean up log4j-api before making a 3.0.0 release. We have > several interfaces that can be merged, and we can take advantage of default > and static methods in interfaces. I suppose a larger modularization or > other overhauls can always be deferred to a 4.0.0 API later on if time > permits. > > On Wed, 27 Jun 2018 at 10:17, Ralph Goers <[email protected]> > wrote: > >> I should have some time this weekend to perform a release of Log4j 2.11.1. >> Just letting you all know in case there is more you would like to get done. >> >> We should also consider when a 3.0.0 release should be done. I’d like to >> make sure that we document the reasons for 3.0.0. Please update the >> announcement file with whatever features you feel were important enough >> that they required a new major release. >> >> Ralph >> > > > -- > Matt Sicker <[email protected]>
