Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Subject: Re: [DISCUSS] EOL for Log4j 1.x
References: 
 <1436002222.2250746.315011689.3282D64D@webmail.messagingengine.com>
 <C5F9365E-320D-453C-A1F0-DBBE5F691963@dslextreme.com>
From: Remko Popma <remko.popma@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <C5F9365E-320D-453C-A1F0-DBBE5F691963@dslextreme.com>
Message-Id: <9E2D7C51-A991-42D4-A40E-EA27BF12EA58@gmail.com>
Date: Sat, 4 Jul 2015 20:03:04 +0900
To: Log4J Developers List <log4j-dev@logging.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Actually I think closing Bugzilla would be a very good idea! I kind of feel s=
orry for all users who diligently put in their error report and how to repro=
duce it etc, when we have no intention to address these issues.=20

That would also serve as one of the methods to clearly signal to the user co=
mmunity that log4j-1.x is EOL.=20
Another one would be to put a notice in the website, of course.=20

Sent from my iPhone

> On 2015/07/04, at 19:42, Ralph Goers <ralph.goers@dslextreme.com> wrote:
>=20
> What is the difference between EOL and the way things are now. Are you pro=
posing that bugzilla would be closed?
>=20
> Ralph
>=20
>> On Jul 4, 2015, at 2:30 AM, Christian Grobmeier <grobmeier@apache.org> wr=
ote:
>>=20
>> Hi all,
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> We can use the remaining time to write or improve documentation, maybe
>> even write some migration tool.
>>=20
>> 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.
>>=20
>> Let me know what you think about this idea. All feedback - committer or
>> not - is welcome.
>>=20
>> 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.
>>=20
>> Regards,
>>=20
>> Christian
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org