Checklist for making a gretl release

Local:
* Update the fedstl database if it needs it
* Ensure the addon zipfiles are up to date with git
* Update lib/src/version.h
* Re-run the configure script in all build directories
* Update src/Changelog and src/CompatLog with the current date
* Commit the above changes to git
* Rebuild and publish the PDF docs
* Rebuild and publish the HMTL docs
* "make dist" to create the new gretl-YYYYx.tar.xz
* Create a new versioned directory in the sourceforge files area
* Make and upload the MS Windows installers (32- and 64-bit)
* Make and upload the macOS installers (intel and arm64)
* Upload a new version of RELEASE to the gretl cgi-bin directory

Remote:
* On sourceforge, make a new versioned subdirectory for gretl,
  and upload the source package as well as the per-platform
  binary packages. Upload a README. Use the SF File
  Manager to mark the new files as the default downloads.
* Also make a new versioned subdirectory of "addons" and
  upload the .zip addon files, if need be.
* Upload to the SF cgi-bin directory a text file named RELEASE
  containing the new version ID, e.g. "gretl-2021d"

Local:
* Update all the web docs (this is automated: ./update_html)
  and upload them to sourceforge
* Update the libgretl API docs and upload ("apipack")
* Send a message to gretl-announce

Allin Cottrell
last revised, May 2021
