From 8f91598227191362ef6575723cc65e347ba7c668 Mon Sep 17 00:00:00 2001
From: falkTX <falktx@gmail.com>
Date: Thu, 21 Dec 2017 16:28:28 +0000
Subject: [PATCH] Update news

---
 News.php            | 23 +++++++++++++----------
 includes/footer.php | 17 ++++++++---------
 2 files changed, 21 insertions(+), 19 deletions(-)

diff --git a/News.php b/News.php
index d3e571f..9a67f19 100644
--- a/News.php
+++ b/News.php
@@ -18,7 +18,10 @@ include_once("includes/header.php");
 </p>
 <p>
     A few days ago a new version of JACK2 was released.<br/>
-    The official changelog is:
+    You can grab the latest release source code at
+        <a href="https://github.com/jackaudio/jack2/releases" target="_blank">
+            https://github.com/jackaudio/jack2/releases</a>.<br/>
+    The official changelog is:<br/>
 </p>
 <ul>
     <li>Fix Windows build issues</li>
@@ -31,24 +34,24 @@ include_once("includes/header.php");
     So this latest release was brought to you by yours truly. ;)<br/>
 </p>
 <p>
-    The release was actually already tagged on the git repo quite some time ago, but I was waiting to see Windows builds were possible.<br/>
+    The release was actually already tagged on the git repo quite some time ago, but I was waiting to see if Windows builds were possible.<br/>
     I got side-tracked with other things and 1.9.12 ended up not being released for some time, until someone reminded me of it again... :)<br/>
     There are still no updated macOS or Windows builds, but I did not want to delay the release further because of it.<br/>
     The 1.9.11 release (without RC label) was skipped to avoid confusion with the versions.<br/>
     So 1.9.12 is the latest release as of today. macOS and Windows binaries still use an older 1.9.11 version.
 </p>
 <p>
-    Being the maintainer of both JACK1 and JACK2 means I can (more or less) decide where to take JACK today forward.<br/>
-    I believe a lot of people are interested to know these plans.<br/>
+    Being the maintainer of both JACK1 and JACK2 means I can (more or less) decide the future of JACK.<br/>
+    I believe a lot of people are interested to know the current plan.<br/>
 </p>
 <p>
-    Fist, JACK1 is in a bug-fix only at the moment.<br/>
-    I want to keep it as the go-to reference implementation of JACK, but do not add any further features to it.<br/>
+    First, JACK1 is in bug-fix mode only.<br/>
+    I want to keep it as the go-to reference implementation of JACK, but not add any new features to it.<br/>
     The reason for this is to try to get JACK1 and JACK2 to share as much code as possible.<br/>
     Currently JACK2 includes its own copy of JACK headers, examples and utilities, while JACK1 uses sub-repositories.<br/>
     During the course of next year (that is, 2018) I want to get JACK2 to slowly use the same stuff JACK1 does, then switch to use the same repositories as submodules like JACK1 does.<br/>
     This will reduce the differences between the 2 implementations, and make it a lot easier to contribute to the examples and utilities provided by JACK.<br/>
-    (Not to mention having utilities that work in slightly different ways)<br/>
+    (Not to mention the confusion caused by having utilities that work in simlar yet different ways)<br/>
     We will keep JACK1 "frozen" until this is all done.<br/>
 </p>
 <p>
@@ -56,12 +59,12 @@ include_once("includes/header.php");
     A few things were added into JACK1 after JACk2 was created, that never made it into JACK2.<br/>
     This includes meta-data (JACK2 does have the API, but a non-functional one) and the new internal clients.<br/>
     The purpose is to reduce reasons users might have to switch/decide between JACK1 and JACK2.<br/>
-    JACK2 should have all features that JACK1 has, and users will opt for JACK2 on pretty much all cases.
+    JACK2 should have all features that JACK1 has, so that most users choose JACK2.<br/>
 </p>
 <p>
-    Now, you likely get the (right) impression that focus is on JACK2.<br/>
+    Now, you are probably getting the impression that the focus will be on JACK2, which is correct.<br/>
     Though I realize some developers might prefer JACK1's design, the long "battle" of JACK1 and JACK2 needs to stop.<br/>
-    Development of new features will happen on JACK2's code, and JACK1 will slowly become legacy.<br/>
+    Development of new features will happen in the JACK2 codebase, and JACK1 will slowly become legacy.<br/>
     Well, this is my personal plan at least.<br/>
 </p>
 <p>
diff --git a/includes/footer.php b/includes/footer.php
index e4564ca..01cc49f 100644
--- a/includes/footer.php
+++ b/includes/footer.php
@@ -31,6 +31,14 @@
             <div class="box box-shadow alpha clear-both navigation">
                 <h2 class="box-header"> <a href="<?php echo $ROOT; ?>/News" style="color: #aaf;">News</a> </h2>
 
+                <a href="<?php echo $ROOT; ?>/News/?action=view&url=jack2-1912-release-and-future-plans">
+                    <b>JACK2 1.9.12 release and future plans</b><br/>
+                </a>
+                <p>
+                    A new version of JACK2 was released, and plans for 2018 defined.
+                </p>
+                <hr/>
+
                 <a href="<?php echo $ROOT; ?>/News/?action=view&url=breaking-changes-in-carla-plugin-host">
                     <b>Breaking changes in Carla Plugin Host</b><br/>
                 </a>
@@ -55,15 +63,6 @@
                     It's time for another KXStudio ISO release!<br/>
                     KXStudio 14.04.5 is here!
                 </p>
-                <hr/>
-
-                <a href="<?php echo $ROOT; ?>/News/?action=view&url=carla-20-beta5-is-here">
-                    <b>Carla 2.0-beta5</b><br/>
-                    <img src="<?php echo $ROOT; ?>/screenshots/carla.png" alt="" width="150px"/>
-                </a>
-                <p>
-                     The 5th beta of the upcoming Carla 2.0 release.
-                </p>
             </div>
         </div>
 <?php } ?>