Initial writeup for jack2 release

News.php

@@ -12,6 +12,66 @@ include_once("includes/header.php");
     <a href="<?php echo $ROOT; ?>/News/?action=feed"><img src="images/rss.png" alt="RSS"/></a>
 </div>
 
+<p>
+    <span style="font-size: 20px">&gt; JACK2 1.9.12 release and future plans</span><br/>
+    On <i>2017-12-21</i> by<i> falkTX</i>
+</p>
+<p>
+    A few days ago a new version of JACK2 was released.<br/>
+    The official changelog is:
+</p>
+<ul>
+    <li>Fix Windows build issues</li>
+    <li>Fix build with gcc 7</li>
+    <li>Show hint when DBus device reservation fails</li>
+    <li>Add support for internal session files</li>
+</ul>
+<p>
+    If you did not know already, I am now maintaining JACK2 (and also JACK1).<br/>
+    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/>
+    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/>
+</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/>
+    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/>
+    We will keep JACK1 "frozen" until this is all done.<br/>
+</p>
+<p>
+    Second, but not least important, is to get the JACK1 specific features into JACK2.<br/>
+    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.
+</p>
+<p>
+    Now, you likely get the (right) impression that focus is on JACK2.<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/>
+    Well, this is my personal plan at least.<br/>
+</p>
+<p>
+    Not sure if this all can be done in 2018, but better to take things slowly and get things done than do nothing at all.<br/>
+    I will keep you updated on the progress through-out the year.<br/>
+    Happy holidays everyone!<br/>
+</p>
+
+<hr/>
+
 <p>
     <span style="font-size: 20px">&gt; Breaking changes in Carla Plugin Host</span><br/>
     On <i>2017-11-21</i> by<i> falkTX</i>