Begin forwarded message:
From: Curt Arnold <[EMAIL PROTECTED]>
Date: August 14, 2006 12:41:19 AM CDT
To: [EMAIL PROTECTED]
Subject: Logging Services August 2006 Report
Logging Services report 2006-08
-------------------------------
Projects listed in alphabetical order.
Overall
----------
* The Logging Services PMC continues to track projects under
incubation:
log4net, log4php.
* Mark Womack resigned as PMC chair and Curt Arnold was appointed
by the Board
after nomination by the PMC to assume the office.
* There has been some recent discussion on a recurring topic of
logging for Javascript.
There are several log4j-like Javascript implementations in the
wild and the
authors of at least one of them has expressed an interest in
contributing to
an ASF effort in that space. The next step would be to attempt
to gather a
Javascript logging interest group to decide what, if anything,
that would be beneficial
for Logging Services to do in that space.
* Logging Services is currently structured as a "umbrella"
project. There was
some discussion long time ago about modifying the bylaws of the
project so that
it is a single project with multiple products and I expect to
reraise the issue
shortly.
log4cxx Report
--------------
* An initial ASF release of log4cxx is long overdue. There only
some minor bug
fixes this quarter and there still needs to be a coordinated
sprint to address
the few remaining issues that have been blocking a release. The
user community
remains healthy, but development has been resource starved.
log4j Report
------------
* A log4j 1.2.14 release candidate is expected shortly. The
consensus had been to
end the log4j 1.2 version with log4j 1.2.13, however there have
been several
significant concurrency issues repeated encountered by the user
community
and fixed in the SVN that should justify reconsidering that
decision.
* A log4j 1.3 alpha 9 release is also expected shortly. Several
binary compatibility
issues with log4j 1.2 have been resolved since the last release.
A contributed alternative
set of appenders that address some reentrancy and concurrency
issues were moved
from the sandbox to the trunk for wider distribution and feedback.
log4net Report
--------------
* The log4net project is still in incubation.
* Work continues on the next point release containing minor bug
fixes. We
are evaluating several enhancements that take advantage of the new
features in .NET 2.0. This raises backwards compatibility questions.
* We have an open ended discussion on the use and storage of strong
name
assembly signing keys. This may need further discussion at wider
level,
and probably requires some sort of consensus amongst all the .NET
projects.
log4php Report
--------------
* No report available from log4php committers in time for this
report. The mailing
list have been very quiet with only 7 messages on the user list
and no messages
on the development list.
