documentation updates

handbook/troggle/trogstatus.html

@@ -32,7 +32,7 @@ the same version of django, then upgrade to as recent a version of django as we
 discovered that django1.7 works just fine with  <a href="https://docs.djangoproject.com/en/1.10/topics/python3/">python3</a>, so we will move the development version to python3 during June and
 then upgrade the server operating system from Debian <var>stretch</var> to <var>buster</var> before
 tackling the next step: thinking deeply about when we migrate from django 
-<a href="trogdesignx.html">to something else</a>.
+<a href="trogdesign.html">to something else</a>.
 </p>
     <p>
 Enforced time at home is giving us a new impetus to writing and restructuring the documentation for everything.
@@ -43,8 +43,13 @@ In the course of these migrations several unused or partly-used django plugins w
 <p>Missing troggle functions were repaired and partly-implemented pages, such as the list of all cavers and their surveyed passages, were finished and made to work. The logbook parsing acquired a cacheing system to re-load pre-parsed files. The survex file parsing was completely rebuilt to reduce the excessive memory footprint. While doing so the parser was extended to cover nearly the full range of survex syntax and modified to parse, but not store, all the survey stations locations. A great many unused classes and some partly written code ideas were deleted.
 <h4>July 2020</h4>
 <p>Wookey upgraded debian on the server from 9 <var>stretch</var> to 10 <var>buster</var> and we got the python3 development of troggle running as the public version (with some http:// and https:// glitches) by 23rd July. <var>Buster</var> will be in-support definitely until June 2024 so we are rather pleased to be on a "not ancient" version of the operating system at last. This concided with a last tweak at improving the full cave data file import so now it runs on the server in ~80 seconds. Which is considerably more useful than the ~5 hours it was taking earlier this year.
-<p>We plan to stick with debian 10 <var>buster</var>, django 1.11.29 and python 3.7.5 (the standard on <var>buster</var>) until spring 2021 when we may upgrade debian to the forthcoming stable release 11 <var>bullseye</var>. At that point debian will have python 3.8 as standard and we will migrate to django 2.x, hopefully getting as far as django 2.2 which is an LTS and actually in support until April 2022.
-<p>With any luck that will be the last of our involvement with django migrations as we may not move on from using django 2.2 until we stop using django altogether, see <a href="trogspeculate.html">troggle architecture speculations</a>.
+
+
+<h4>April 2021</h4>
+<p>Lockdown has been good to troggle. During March and April Philip migrated troggle up to Django 2.2.19, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookie discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary obstensibly outdated link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.</p>
+<p>We plan to stick with this configuration for a year.</p>
+<p>Next April (2022) we may to the forthcoming debian stable release 11 <var>bullseye</var>. At that point debian will have python 3.8 as standard and we also hope to migrate to django 3.2 LTS which will be a year old by then and which will be <a href="https://www.djangoproject.com/download/#supported-versions">supported until April 2025</a>.
+    <p>With any luck that will be the last of our involvement with django migrations as we may not move on from using django 3.2 until we stop using django altogether, see <a href="trogspeculate.html">troggle architecture speculations</a>.
 <hr />
 <img  border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
 Return to: <br />