This provides instructions for publishing a new guiguts release on Github.
-
Ensure the version of ebookmaker to be bundled with the Windows release is the latest version as used online at PG. Build and release the latest version using the ebm_builder repo. Set the correct ebookmaker version number in
tools/ebookmaker/package.sh
-
Update the guiguts version. This needs to happen in two places:
Makefile
guiguts.pl
-
Update the
CHANGELOG.md
-
Commit the version update changes and tag the release (ie:
git tag r<version>
) and push it up to github -
From a Linux or MacOS system, or a Windows system with MinGW installed, confirm that you are working from a clean git checkout. Then build the three releases using
make
ormake all
ormake win make mac make generic
This creates three .zip files, one for each platform.
Be certain to keep the format
guiguts-platform-1.0.0.zip
(platform and version number will vary) in order for the update mechanism to work correctly. Do not includesettings.rc
orheader.txt
as these may have been modified by the user and will be created if they do not exist. TheMakefile
takes care of this. -
Publish the release on Github.com
- Log into github.com
- Access the guiguts releases
- Select Draft a new release
- Specify the tag (ie:
r<version>
) - Specify the title (ie:
<version>
) - Describe the release - can be a copy/paste of the
CHANGELOG.md
details for the release - Attach the .zip files
- Publish release