It was mentioned on a mailing list or twitter conversation with maintainers of another Apache project that one of the reasons they hesitate to migrate to Log4j is that they worry we will break binary compatibility.
Removing the factory methods just because we deprecated them seems a bit harsh. It's not like it's a huge maintenance effort to keep them. I would not remove the deprecated factory methods unless they actively prevent us from doing something we want to do. Remko Sent from my iPhone > On 2016/09/02, at 6:29, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Well, Java seems to have a policy of waiting at least 10 years, if ever…. > > Seriously, I don’t think 1 minor release is enough as that might very well be > the next release. I’d say 2 minor releases and at least 6 months. > > Ralph > >> On Sep 1, 2016, at 1:42 PM, Matt Sicker <boa...@gmail.com> wrote: >> >> I think that when you add a builder and deprecate the factory, you should >> remove it in the next 2.x release. Otherwise, deprecation has no point if >> there's no version with the deprecation specified. >> >> On 1 September 2016 at 13:40, Gary Gregory <garydgreg...@gmail.com> wrote: >>> Hi, >>> >>> When can we delete factory methods that are deprecated by builders? >>> >>> Gary >>> >>> -- >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>> Java Persistence with Hibernate, Second Edition >>> JUnit in Action, Second Edition >>> Spring Batch in Action >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> >
