As Remko mentioned, I think making Bugzilla "readonly" and noting on the website there will be no activity on 1x anymore. Currently some people may hope we get a new release done. With EOL we simply say: there is no sense anymore to wait. Move on.
Please see what Struts did here: http://struts.apache.org/ It's basically what I recommend. Thanks! On Sat, Jul 4, 2015, at 13:03, Remko Popma wrote: > Actually I think closing Bugzilla would be a very good idea! I kind of > feel sorry for all users who diligently put in their error report and how > to reproduce it etc, when we have no intention to address these issues. > > That would also serve as one of the methods to clearly signal to the user > community that log4j-1.x is EOL. > Another one would be to put a notice in the website, of course. > > Sent from my iPhone > > > On 2015/07/04, at 19:42, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > > > What is the difference between EOL and the way things are now. Are you > > proposing that bugzilla would be closed? > > > > Ralph > > > >> On Jul 4, 2015, at 2:30 AM, Christian Grobmeier <grobme...@apache.org> > >> wrote: > >> > >> Hi all, > >> > >> we are actively working on Log4j 2.x, but Log4j 1.x hasn't been touched > >> since the last release. I was doing the last one, and I can't see I will > >> find the time or motivation in any time to roll out another one. Nobody > >> else stood up since then. That's OK, because I can observe the community > >> adapting Log4j 2. No numbers, just feelings. > >> > >> I would like to propose to mark an EOL date for Log4j 1.x by the end of > >> the year. As we don't fix things (most likely) with 1.x, this is not > >> about "maintenance" at all. The future date might be more or less our > >> signal that we want to actively help our users migrating to 2.x. > >> > >> We can use the remaining time to write or improve documentation, maybe > >> even write some migration tool. > >> > >> In the announcement we should highlight the history of Log4j 1, it's > >> problems and why we think Log4j 2.x is the best way to log in Java > >> today. > >> > >> Let me know what you think about this idea. All feedback - committer or > >> not - is welcome. > >> > >> I suggest we leave this discussion open until we reached an agreement or > >> at least one week, so everybody got a chance to look into this. > >> > >> Regards, > >> > >> Christian > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
