remove mentions of 1.7.8

3 files changed, 14 insertions, 19 deletions

diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html
index c1038aed..31eecdd7 100755
--- a/slf4j-site/src/site/pages/codes.html
+++ b/slf4j-site/src/site/pages/codes.html
@@ -92,15 +92,15 @@
     <h3 class="doAnchor" name="loggerNameMismatch">Detected logger
     name mismatch. </h3>
 
-    <p><span class="label notice">Note</span> Logger name mismatch
-    warnings are printed only if the
+    <p>Logger name mismatch warnings are printed only if the
     <code>slf4j.detectLoggerNameMismatch</code> system property is set
     to true. By default, this property is not set and no warnings will
     be printed even in case of a logger name mismatch.
     </p>
 
-    <p>The warning will be printed in case the name of the logger
-    specified via a class passed as an argument to the
+    <p><span class="label">since 1.7.9</span> The warning will
+    be printed in case the name of the logger specified via a class
+    passed as an argument to the
     <code>LoggerFactory.getLogger(Class)</code> method differs from
     the name of the caller as computed internally by SLF4J.
     </p>
diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html
index 042a4799..ed645fc5 100755
--- a/slf4j-site/src/site/pages/manual.html
+++ b/slf4j-site/src/site/pages/manual.html
@@ -53,7 +53,7 @@
     users are highly encouraged to migrate to SLF4J 1.7.5 or later.
     </p>
 
-    <p><span class="label">since 1.7.8</span> By setting he
+    <p><span class="label">since 1.7.9</span> By setting he
     <code>slf4j.detectLoggerNameMismatch</code> system property to
     true, SLF4J can automatically <a
     href="codes.html#loggerNameMismatch">spot incorrectly named
diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html
index cc686d8e..4b5b60de 100755
--- a/slf4j-site/src/site/pages/news.html
+++ b/slf4j-site/src/site/pages/news.html
@@ -29,18 +29,7 @@
 
    <hr noshade="noshade" size="1"/>
 
-   <h3>16th of December, 2014 - Release of SLF4J 1.7.8</h3>
-
-   <p>The introduction of the @Nonnull JSR 305 annotation in SLF4J
-   version 1.7.8 causes the Scala compiler to fail. This is issue has
-   been documented in <a
-   href="https://issues.scala-lang.org/browse/SI-5420">SI-5420</a>. Given
-   that many Scala users will be affected by this issue for the
-   foreseeable future, we have decided to renounce the user of JSR 305
-   annotations in SLF4J for the time being.
-	 </p>
-
-   <h3>14th of December, 2014 - Release of SLF4J 1.7.8</h3>
+   <h3>16th of December, 2014 - Release of SLF4J 1.7.9</h3>
 
    <p class="highlight"><a href="codes.html#loggerNameMismatch">Spot
    incorrectly named loggers</a> by setting the
@@ -62,8 +51,14 @@
    org.apache.log4j.MDC in the log4j-over-slf4j module.
    </p>
 
-   <p>Added JSR305 @Nonnull annotations in <code>LoggerFactory</code>
-   class. Further annotations are likely to follow.</p> 
+   <p>The introduction of the @Nonnull JSR 305 annotation in SLF4J
+   version 1.7.8 causes the Scala compiler to fail. This is issue has
+   been documented in <a
+   href="https://issues.scala-lang.org/browse/SI-5420">SI-5420</a>. Given
+   that many Scala users will be affected by this issue for the
+   foreseeable future, we have decided to renounce the user of JSR 305
+   annotations in SLF4J for the time being.
+	 </p>
 
    <p>Numerous small code improvements too minor to be listed
    here.</p>