# update the version number in the changelog if not already done:

grep -q "$(COREVERSION)" ../CHANGELOG.md || \

sed "/^## \[Unreleased\]/ a\\\n\n## [$(COREVERSION) - $(DATE)]" ../CHANGELOG.md

git add ../CHANGELOG.md

git add parts/tools-*-$(SDCCVERSION).txt parts/tools-*-$(TOOLSVERSION).txt parts/platform-*-$(COREVERSION).txt

git commit

git tag v$(COREVERSION)

Tools for a simple release management system.

Mimimizing the amount of manual work needed for generating the board manager

release files hopefully minimizes the number of errors and allows for

frequent releases.

- Update the version number for the updated components in `Makefile`.

- `make`

- `make upload`: test on local test server

- Check Changelog. No need to update the version number.

- `make release`: Update version number in changelog, commit generated

files, tag the new release.

- release message on github and attach the files in release/<VERSION>/

The main `Makefile` defines the version numbers for the core, sdcc and the

tools. Update the version number for the component you would like to

re-generate and run `make`.

It is helpful to really edit the Makefile and save the new version numbers

to the repository on every release. This will make sure that all

dependencies are up-to-date the next time and will prevent the system from

using references to old versions.

After testing, check in the newly generated files and update the Changelog:

make release

For testing purposes only (!!), it is possible to use the simpler systax

using makefile variables on the command line:

make COREVERSION=0.3.2 core

will generate a fresh archive for the core files and update the package file

accordingly.