Release 0.2.0-rc.1

The first release candidate of 0.2.0: DNSSEC signing and Porkbun
support, two-factor login, view colours and navigation, and the build
shown in a footer. Its notes are the CHANGELOG's Unreleased section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -166,9 +166,11 @@ review step.
 
 ## Status
 
-Version 0.1.0, the first release. It is feature-complete for one server's
+Version 0.2.0 is in testing (0.2.0-rc.1); 0.1.0 is the current release.
-configuration. DNSSEC signing and managing several servers are not handled
+0.2.0 adds DNSSEC signing, Porkbun support, two-factor login and view
-yet ([concepts.md](docs/concepts.md#what-jarl-deliberately-doesnt-do-yet)).
+colours. Jarl is feature-complete for one server's configuration.
+Managing several servers from one jarld and dynamic updates are not
+handled yet ([concepts.md](docs/concepts.md#what-jarl-deliberately-doesnt-do-yet)).
 
 ## License
 

VERSION

@@ -1 +1 @@
-0.1.0
+0.2.0-rc.1

docs/install.md

@@ -387,9 +387,12 @@ sudo apt update && sudo apt upgrade      # Debian packages from the registry
 make && sudo make install && sudo systemctl restart jarl   # make install
 ```
 
-Database migrations run automatically at startup. Before an upgrade, take
+Database migrations run automatically at startup. An older Jarl refuses
-a backup (it is safe while jarld runs); `jarld restore` puts it back if
+to start on a database a newer one has upgraded ("database schema version
-needed:
+4 is newer than this Jarl"). So going back to an earlier version, after
+trying a release candidate say, means restoring a backup taken before the
+upgrade. Before an upgrade, take a backup (it is safe while jarld runs);
+`jarld restore` puts it back if needed:
 
 ```sh
 sudo jarld backup