[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-13T10:17:43 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -6,7 +6,7 @@ == Status == -RELEASE PLAN: release branch taken, starting release candidate preparations +RELEASE PLAN: Release candidate 1 available @@ -78,6 +78,7 @@ 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'' = Post Release = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-12T09:55:29 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -64,6 +64,14 @@ Any changes made after the branch is taken and code frozen will be added as they are made. +''DONE'' + +== VOTE Process == + +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 CandidateElection be used as the approval process for this release. + == Release Candidate == 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-12T09:56:43 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -66,11 +66,11 @@ ''DONE'' -== VOTE Process == +== Approval Process == 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 CandidateElection be used as the approval process for this release. +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. == Release Candidate == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-08T14:57:46 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan Updated release status Change Log: -- @@ -6,7 +6,7 @@ == Status == -RELEASE PLAN: preparing for release branch +RELEASE PLAN: release branch taken, starting release candidate preparations @@ -16,11 +16,13 @@ == Documentation Review == - * Ensure that javadocs and website are up to date. + * 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) == Bug Review == +''DONE'' (thanks Dennis) + * Bug 28291 ''[logging] Context``Class``Loader 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. @@ -55,6 +57,8 @@ == Repository == 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. + +''DONE'' == Release Notes == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-07T13:08:12 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan Updated plan to reflect work done Change Log: -- @@ -6,7 +6,7 @@ == Status == -RELEASE PLAN is stalled (my much-loved cube blew up) +RELEASE PLAN: preparing for release branch @@ -17,7 +17,7 @@ == Documentation Review == * Ensure that javadocs and website are up to date. - * The new optional distribution which offers enhanced memory recycling in some environments needs documentation creating. + * The new optional distribution which offers enhanced memory recycling in some environments needs documentation creating. ''DONE'' (thanks brian) == Bug Review == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-02-01T14:40:42 Editor: RobertBurrellDonkin Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan note about status of plan Change Log: -- @@ -6,7 +6,7 @@ == Status == -RELEASE PLAN is waiting on conversion of repository to subversion +RELEASE PLAN is stalled (my much-loved cube blew up) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-01-26T14:32:43 Editor: 82.38.65.173 Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan Updated release plan Change Log: -- @@ -6,7 +6,7 @@ == Status == -DRAFT RELEASE PLAN UNDER DEVELOPMENT +RELEASE PLAN is waiting on conversion of repository to subversion @@ -22,13 +22,21 @@ == Bug Review == * Bug 28291 ''[logging] Context``Class``Loader 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 Log``Factory 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. + * +1 * 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.Log4j``Factory.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) == Bug Fix == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-01-23T03:15:08 Editor: DennisLundberg Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -21,6 +21,15 @@ == Bug Review == + * 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. + * 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. + * Bug 30268 ''[logging] Add CLDC support''. Involves major changes - move to 1.1. + * Bug 30632 ''[logging] print/display the wire log!'' Related to using commons-logging in httpclient. Might be a documentation issue. + * Bug 31286 ''[logging] Memory leaks in JBoss due to LogFactory cache''. Almost done. Requires some documentation according to the comments. + * 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. + * Bug 32691 ''[logging] Convenience methods for cleaner application code''. Involves API changes. Will have to wait for a later release. + == Bug Fix == == Test Compatibility == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-01-23T03:22:17 Editor: DennisLundberg Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -21,13 +21,13 @@ == Bug Review == - * 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. + * Bug 28291 ''[logging] Context``Class``Loader 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. * 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. * Bug 30268 ''[logging] Add CLDC support''. Involves major changes - move to 1.1. * Bug 30632 ''[logging] print/display the wire log!'' Related to using commons-logging in httpclient. Might be a documentation issue. - * Bug 31286 ''[logging] Memory leaks in JBoss due to LogFactory cache''. Almost done. Requires some documentation according to the comments. + * Bug 31286 ''[logging] Memory leaks in JBoss due to Log``Factory cache''. Almost done. Requires some documentation according to the comments. * 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. + * 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.Log4j``Factory.java is attached. * Bug 32691 ''[logging] Convenience methods for cleaner application code''. Involves API changes. Will have to wait for a later release. == Bug Fix == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Commons Wiki] Updated: Logging/1.0.5ReleasePlan
Date: 2005-01-20T15:01:03 Editor: 82.38.65.173 Wiki: Jakarta Commons Wiki Page: Logging/1.0.5ReleasePlan URL: http://wiki.apache.org/jakarta-commons/Logging/1.0.5ReleasePlan no comment Change Log: -- @@ -6,7 +6,7 @@ == Status == -RELEASE PLAN UNDER DEVELOPMENT +DRAFT RELEASE PLAN UNDER DEVELOPMENT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
