How to start a new update train

Sometimes, existing versions of Anathema must not automatically update to later versions.
Reasons for this range from dropped rules, i.e. we decide to stop supporting an old edition, or a technical change, i.e. we require a later Java version and Anathema might not work properly if it is not installed.

To make this happen

1. Switch the URL of the downloads.
   Currently, updates are hosted at http://anathema.butatopanto.de:8081/updates/, and simply offering later versions at another URL like http://anathema.butatopanto.de:8081/updates2/ would effectively hide them from the update-mechanism. You don't have to create the new location on the server (the build will take care of it), but if you do, it helps Anathema to show that there are no more recent versions available. If you do, make sure that all files and folders belong to the user anathema, not your own user.

2. Tell current users.
   We can't force them to read, but we can at least make sure to reach a reasonable part of the community. To that end, we use the update screen. It displays our release notes, and thus, if we add one last version to the OLD URL, it shows that version's changelog to everyone who tries to update.
   Now all we have to do is to make that changelog spell "Later versions of Anathema will [not support xxx|require yyy], please re-install the program if you are cool with that change." and hope that people read it.