GpgFrontend's New Version Model and Release Mechanism
Updates have always been one of GpgFrontend’s biggest pain points. From the very first versions, GpgFrontend relied on GitHub Release to publish versions and to check for updates, and it stayed that way for many years. Starting with 2.2.5, and including the current main line, the version numbering rules, the release process and the way the client checks for updates have all moved to a new model and mechanism. How to use it and how to verify things is already in the user manual. But why I did it this way, and what I was thinking at the time, doesn’t come across in the documentation. ...