Can we please keep a running history in the release notes? IOW, never delete 
text. If I am updating from 2.0 to 2.1, I want to know everything that also 
happens in 2.0.1 and 2.0.2.

I see other projects do that and it is really helpful. The newest release is at 
the top.

Gary

<div>-------- Original message --------</div><div>From: [email protected] 
</div><div>Date:08/16/2014  23:25  (GMT-05:00) </div><div>To: 
[email protected] </div><div>Subject: svn commit: r1618449 - in 
/logging/log4j/log4j2/trunk: RELEASE-NOTES.txt
  src/changes/changes.xml </div><div>
</div>Author: mattsicker
Date: Sun Aug 17 03:25:28 2014
New Revision: 1618449

URL: http://svn.apache.org/r1618449
Log:
Update release notes and changes for 2.0.2.

Modified:
    logging/log4j/log4j2/trunk/RELEASE-NOTES.txt
    logging/log4j/log4j2/trunk/src/changes/changes.xml

Modified: logging/log4j/log4j2/trunk/RELEASE-NOTES.txt
URL: 
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/RELEASE-NOTES.txt?rev=1618449&r1=1618448&r2=1618449&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/RELEASE-NOTES.txt (original)
+++ logging/log4j/log4j2/trunk/RELEASE-NOTES.txt Sun Aug 17 03:25:28 2014
@@ -1,46 +1,43 @@

-              Apache Log4j 2.0.1 RELEASE NOTES
+              Apache Log4j 2.0.2 RELEASE NOTES

-The Apache Log4j 2 team is pleased to announce the Log4j 2.0.1 release!
+The Apache Log4j 2 team is pleased to announce the Log4j 2.0.2 release!

Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
many of the improvements available in Logback while fixing some inherent 
problems in Logback's
architecture.

-This is the first GA release, after thirteen prior releases over the last 4 
years.
+This is the third GA release which contains several bugfixes from the previous 
release.

-?
+Bug fixes and enhancements

Changes in this version include:

-New features:
-o LOG4J2-725:  Added WebLoggerContextUtils class to log4j-web for helper 
methods useful for asynchronous servlets. 
-o LOG4J2-710:  Added documentation for Custom Levels and Custom Loggers. 

Fixed Bugs:
-o LOG4J2-744:  Avoid unnecessary Clock calls when TimestampMessage is logged. 
Thanks to Scott Harrington. 
-o LOG4J2-704:  Improved error message if configuration file not found. 
-o LOG4J2-750:  Webapp configuration page has incorrect class name. Thanks to 
Mike Calmus. 
-o LOG4J2-749:  Retain the default date pattern after fixing the ISO8601 
pattern. Thanks to Scott Harrington. 
-o LOG4J2-670:  DatePatternConverter ISO8601_PATTERN now conforms to ISO8601. 
-o LOG4J2-741:  Reinstate the package configuration attribute for discovering 
custom plugins. 
-o LOG4J2-742:  XInclude not working with relative path. Thanks to Pascal 
Chollet. 
-o LOG4J2-740:  Fixed typo in webapp manual regarding sample web.xml file. 
Thanks to Kosta Krauth. 
-o LOG4J2-738:  RollingFileManager deadlock if async action thread fails to 
start. Thanks to Timothy Stack. 
-o LOG4J2-736:  Fixed log4j-bom so that it won't specify a default scope on any 
third party dependencies. 
-o LOG4J2-735:  Fixed log4j-bom so that it won't interfere with spring-bom and 
others. 
-o LOG4J2-731:  Updated documentation regarding extensions to 
LoggerContextFactory and Log4j 2 providers. 
-o LOG4J2-373:  Fixed ClassLoader issues in loading Log4j providers in an OSGi 
environment. 
-o LOG4J2-719:  Correctly handle NetworkOnMainThreadException thrown on Android 
during Log4j2 initialization. 
-o LOG4J2-716:  Automatically disable log4j JMX when detecting we are running 
on Android. 
-o LOG4J2-657:  Fixed AbstractDatabaseManager to close connection on 
writeInternal error. Thanks to Stefan Wehner. 
-o LOG4J2-713:  Android: java.lang.VerifyError: 
org/apache/logging/log4j/core/util/Closer Thanks to Nelson Melina. 
-o LOG4J2-703:  Android: Could not find class 'javax.naming.InitialContext', 
referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. 
Thanks to Nelson Melina. 
+o LOG4J2-773:  Site: log4j-core component pages were still using the old logo. 
+o LOG4J2-760:  Documentation improvement: link to dependency tree from 
log4j-core component page,
+        link to log4j-core component page from FAQ page. 
+o LOG4J2-679:  Resolved race condition that caused log file rotation to fail 
with error: "Unable to create directory ..." 
+o LOG4J2-726:  Prevent application from hanging when PatternLayout 
configuration has opening '{' but no closing '}'. 
+o LOG4J2-769:  Startup takes a long time if you have empty packages attribute. 
Thanks to Scott Harrington. 
+o LOG4J2-763:  Improved asynchronous loggers and appenders to ensure the 
formatted message does not change even if
+        parameters are modified by the application. (ParameterizedMessage was 
already safe.)
+        Improved documentation. Thanks to Stephen Connolly. 
+o LOG4J2-729:  Emit warning message to console if no configuration file found. 
+o LOG4J2-765:  Improve warning message when missing log4j-core in the 
classpath. 
+o LOG4J2-722:  Clarified in documentation that Commons Logging jar is required 
when using log4j-jcl. 
+o LOG4J2-723:  Clarified in documentation that SLF4J API jar is required when 
using log4j-slf4j-impl. 
+o LOG4J2-759:  Fixed various minor site/documentation issues, mostly 
versioning related. 
+o LOG4J2-756:  Prevent JUnit test from creating unnecessary Log4j2Plugins.dat 
during build. Thanks to Scott Harrington. 
+
+Changes:
+o LOG4J2-775:  Update Apache Flume to 1.5.0.1 from 1.5.0. 
+o LOG4J2-730:  Allow Log4jContextFactory subclasses to specify a custom 
ContextSelector. 


-
-Apache Log4j 2.0.1 requires a minimum of Java 6 to build and run. Basic 
compatibility with
+Apache Log4j 2.0.2 requires a minimum of Java 6 to build and run. Basic 
compatibility with
Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

Modified: logging/log4j/log4j2/trunk/src/changes/changes.xml
URL: 
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/changes/changes.xml?rev=1618449&r1=1618448&r2=1618449&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/changes/changes.xml (original)
+++ logging/log4j/log4j2/trunk/src/changes/changes.xml Sun Aug 17 03:25:28 2014
@@ -21,7 +21,7 @@
     <title>Changes</title>
   </properties>
   <body>
-    <release version="2.0.2" date="2014-0?-??" description="Bug fixes and 
enhancements">
+    <release version="2.0.2" date="2014-08-16" description="Bug fixes and 
enhancements">
       <action issue="LOG4J2-775" dev="ggregory" type="update">
         Update Apache Flume to 1.5.0.1 from 1.5.0.
       </action>


Reply via email to