Commons Logging 1.0.5 ReleasePlan
JCL 1.0.4 was release in July. The 1.0.x codebase is mature and most of the limitations of the design are well understood. A small number of improvements have been made since this release some very important for some use cases. There is now considerable interest in pushing JCL onwards from this codebase. The time seems apt for the release of JCL1.0.5
Release cancelled. After an initial release candidate was created, it was decided to do additional significant work. This new work is being released as version 1.1; see Logging/1.1.0ReleasePlan for details.
Anyone who wants to volunteer for a task, just add something
Ensure that javadocs and website are up to date. DONE
The new optional distribution which offers enhanced memory recycling in some environments needs documentation creating. DONE (thanks brian)
DONE (thanks Dennis)
Bug 28291 [logging] ContextClassLoader may load Log impl from wrong context in JDK 1.4. This one's about classloading and should not be handled in 1.0.5.
- +1 Any solution I had, I've now forgotten...
Bug 30131 [logging] Getting Logger to give trace Information. I made a comment on this one back in July with some suggestions to try for the reporter. No reply was made on those suggestions. I propose we close this one.
- This looks very similar to #30632. Wonder whether there's a bad bit of example code somewhere...
Bug 30268 [logging] Add CLDC support. Involves major changes - move to 1.1.
- +1 Hope that this might be fixable with proposed discovery code
Bug 30632 [logging] print/display the wire log! Related to using commons-logging in httpclient. Might be a documentation issue.
- Looks more like a plea for help than a bug. See if the documentation can be improved
Bug 31286 [logging] Memory leaks in JBoss due to LogFactory cache. Almost done. Requires some documentation according to the comments.
- This will be taken care of by the pre-release work
Bug 32618 [logging] Enterprise Commons Logging : Globalization & more. The new proposal by IBM. Will not be done in this release.
Bug 32662 [logging] Log writer not closed with log4j after restarting a webapp (Tomcat 5.0). A modified version of org.apache.commons.logging.impl.Log4jFactory.java is attached.
- Probably worth investigating and fixing (if possible) for this release
Bug 32691 [logging] Convenience methods for cleaner application code. Involves API changes. Will have to wait for a later release.
- +1 (may want to rolled these ideas into the current discussions)
As a point release, this should be fully backwards compatible. This needs checking.
This will be prepared in the traditional way (by using CVS commit logs).
A release branch will be taken as soon as the preliminary work is complete. This will allow work to continue on HEAD. If possible, this step should be postponed until after jakarta commons is converted to SVN.
Any changes made after the branch is taken and code frozen will be added as they are made.
JCL is very widely used component. Any issues with a new release have the potential for great downstream damage.
Therefore, I would like to propose that CandidateQualityElection be used as the approval process for this release. I believe that this process will give the maximum chance for problems to be detected before they can cause damage to downstream users.
A release candidate will be prepared. Since backwards and future compatibility with Log4J is of crucial importance, users and developers will be asked to test their current installations with the release candidate.
Therefore a suitable gap (to allow this testing) will be left between the announcement of the release and the release vote. Committers will be encouraged to test this RC on their own application before VOTEing +1.
RELEASE CANDIDATE ONE NOW AVAILABLE
Process Bugs Marked Later
- Version compiled on jdk1.4 doesn't seem to work on JDk1.3. Therefore, the jdk14Logger needs to be compiled with 1.4 and everything else with 1.3 for the release.
Up to Logging