what do we do about the current Gump run failures? Seems to be
consistently happening. Anyone know why? If it wasn't for that I'd
say +1, but I feel uncomfortable giving that without some idea as to
why it's suddenly started failing.
thoughts?
Paul
On 26/08/2007, at 12:58 AM, Curt Arnold wrote:
This is a vote on publishing the following artifacts as log4j
1.2.15 and log4j-extras 1.0:
http://people.apache.org/builds/logging/log4j/1.2.15/apache-
log4j-1.2.15_rc6.tar.gz (also .zip)
http://people.apache.org/builds/logging/log4j/companions/extras/1.0/
apache-log4j-extras-1.0_rc5.tar.gz (also .zip)
In addition, updating http://logging.apache.org with the content
now currently staged at:
https://svn.apache.org/repos/asf/logging/site/trunk/docs/index.html
The central Maven repository would be updated with the appropriate
files from http://people.apache.org/builds/logging/repo.
A simultaneous PMC and log4j-dev vote for the log4j releases will
be held on log4j-dev and will be open for at least 72 hours. At
least 3 +1 votes from PMC members are required to proceed with the
release, but comments and votes from other parties are desired.
Here is my +1 to get things started.
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.com
This email and any attachments are intended solely for the addressee.
The contents may be privileged, confidential and/or subject to
copyright or other applicable law. No confidentiality or privilege is
lost by an erroneous transmission. If you have received this e-mail
in error, please let us know by reply e-mail and delete or destroy
this mail and all copies. If you are not the intended recipient of
this message you must not disseminate, copy or take any action in
reliance on it. The sender takes no responsibility for the effect of
this message upon the recipient's computer system.
