Updated release notes to correct issues highlighted by Dennis.

git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@399403 13f79535-47bb-0310-9956-ffa450edef68

RELEASE-NOTES.txt

@@ -142,12 +142,14 @@ override those methods will not have their methods called. This is a pretty
 unusual thing to do, so it isn't expected that any apps will actually be
 affected by this.
 
+AvalonLog is no longer serializable. The semantics were always deeply 
+unsatisfactory. It is cleaner and clearer to admit the truth.
+
 == Deprecation Note ==
 
 Previous releases of commons-logging-api.jar contained the Jdk14Logger class;
 this is now deprecated. It will be removed from the API jar in some future 
-release. If your application needs this jar, then instead of
-upgrading to commons-logging-api-1.1.jar, upgrade to commons-logging-1.1.jar.
+release. 
 
 == Dependencies ==
 
@@ -170,9 +172,11 @@ distribution. This ensures that the core Log/LogFactory classes are only
 deployed via one classloader, thus avoiding "Log4JLogger does not implement Log"
 and similar problems.
 
-File commons-logging-api-nn.jar provides no adapters to external logging
-libraries, just the internally implemented SimpleLog and NoOpLog classes. This
-jar file may be used as a declared dependency for projects that care about
+File commons-logging-api-nn.jar provides minimal adapters to external logging
+libraries, just the internally implemented SimpleLog and NoOpLog classes
+plus Jdk14Logger (which is currently required by Apache Tomcat).
+
+This jar file may be used as a declared dependency for projects that care about
 "transitive dependencies" and can't handle jar files such as commons-logging-nn.jar
 which have "optional" dependencies depending on how they are used. In addition,
 this jar file can be useful for "rebundlers" of JCL who recompile the source-code