Doc. Commit history note for my future understanding: the 19_MAINT branch

was abandonned at this point.  There is not enough new development in trunk
to justify version 1.20, and what there is has seen quite a lot of test
(mostly the code refactoring necessitated by the optional "update only ext
attr metadata" feature). OTOH the python3 code needs to come out to support
the new Unity scope, and I was too lazy to merge it the 19 branch (also a
bit too much mod for a "maintenance" branch). So what would have been
1.20.0 comes out as 1.19.10, on the trunk.

website/download.html

@@ -67,7 +67,7 @@ function showdiv(viewid)
 <div id="general">
 <h2><a name="general">General information</a></h2>
 
-<p>The current version is 1.19.9. <a href="release-1.19.html">Release
+<p>The current version is 1.19.10. <a href="release-1.19.html">Release
 notes</a>.</p>
 
 <p>The download page for Recoll 1.18 is <a href="download-1.18.html">still
@@ -117,12 +117,12 @@ is probably no necessity to upgrade anyway.</p>
 <div id="source">
 <h2><a name="source">Source</a></h2>
 
-<h3>Current release distribution: 1.19.9:</h3>
+<h3>Current release distribution: 1.19.10:</h3>
 <!-- Attention: source packages must remain here, not in a
 subdirectory, because of all the places they're referred from
 (package watches) -->
 
-<p><a href="recoll-1.19.9.tar.gz">recoll-1.19.9.tar.gz</a>. </p>
+<p><a href="recoll-1.19.10.tar.gz">recoll-1.19.10.tar.gz</a>. </p>
 <!--
 <h3>Snapshot</h3>
 <p>I sometimes release a source tarfile when I consider that the
@@ -182,6 +182,7 @@ branch for the current production version.</p>
 <h3>Older recoll releases:</h3>
 
 <p>
+<a href="recoll-1.19.9.tar.gz">1.19.9</a>. 
 <a href="recoll-1.19.8.tar.gz">1.19.8</a>. 
 <a href="recoll-1.19.7.tar.gz">1.19.7</a>. 
 <a href="recoll-1.19.5.tar.gz">1.19.5</a>.