Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: log4j on JDK 1.5 (on Gump)
Date: Thu, 2 Sep 2004 08:46:46 -0400
Message-ID: <9C5166762F311146951505C6790A9CF80229BFF2@US-VS1.corp.mpi.com>
Thread-Topic: log4j on JDK 1.5 (on Gump)
Thread-Index: AcSQSCJBHd8Vnd6xQGmmVJYTK/w+kAAJADPwAB+VoTA=
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>


H=
ola,
I think we could just add source=3D"1.4" to the javac calls in build.x=
ml
and be done with it (i.e. no code changes needed).

As far as being Release Manager: you'd have to tag in CVS, build the
releases, sign them (and make sure your PGP key is in the KEYS file in=

the distro), upload the dist to the repository on
/www/www.apache.org/dist (and /www/archive.apache.org/dist), make the
community aware (email log4j-dev, log4j-user, pmc@logging,
general@apache), and that's mostly it.

But I'm not convinced we should do a release.  1.2.8 is nice and stabl=
e,
and if it's between getting a 1.3.0 alpha out and doing 1.2.9, I'd
prefer a 1.3.0.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Paul Smith [mailto:psmith@aconex.com]
>Sent: Wednesday, September 01, 2004 5:42 PM
>To: 'Log4J Developers List'
>Subject: RE: log4j on JDK 1.5 (on Gump)
>
>> >Which brings the question of, do we need to do this enum keyword
>> >replacement (not a big deal) in the log4j 1.2 branch and possibly
have a
>> >log4j 1.2.9 release that's compatible with JDK 1.5 / 5.0?
>>
>> No, I don't think it's worth the effort.
>While I agree that it is a bit of a pain, I think it's something that=

>people
>are going to want.  I have a feeling there will be a high number of
people
>using 1.5.
>What is involved in a 'release'?  I would be happy to put in the
effort, if
>someone could give me an 'administrative TODO list'(other than the
branch/
>and fixing the code).
>Cheers,
>Paul Smith
>
>
>---------------------------------------------------------------------=

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


This e-mail, including any attachments, is a confidential business com=
munication, and may contain information that is confidential, propriet=
ary and/or privileged.  This e-mail is intended only for the individua=
l(s) to whom it is addressed, and may not be saved, copied, printed, d=
isclosed or used by anyone else.  If you are not the(an) intended reci=
pient, please immediately delete this e-mail from your computer system=
 and notify the sender.  Thank you.


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