although I'm not 100% sure logging alone would warrant it becoming 3.0...
although logging is coming to the branch soon, and I would prefer not having it waiting for releases... it's a significant improvement for how we develop the codebase. On Fri, Sep 16, 2022 at 11:40 AM Clebert Suconic <clebert.suco...@gmail.com> wrote: > > On Fri, Sep 16, 2022 at 11:05 AM Justin Bertram <jbert...@apache.org> wrote: > > > > In my opinion there is a bit of more work to do before 3.0 could be > > released. For example: > > > > - Remove all deprecated methods, config, etc. (this is not a small amount > > of work) > > - Update all the config with the new inclusive terms > > > > Personally I don't really see how we could do the logging change on 2.x as > > it's a breaking change. Folks won't be able to follow the normal upgrade > > procedure [1] since it will break their logging configuration. > > We have broken migration between versions before with a release notes > instruction. I don't see anything different. > > Logging changes are coming now... if we have to make it 3.0 now, and > 4.0 later would be the full term of changes.. So that's what I would > prefer to do. -- Clebert Suconic
