Contents
Development
In order to build and test your changes, simply run ./scripts/develop
.
Documentation is generated from the sql files, using the script scripts/documentaion
(requires poetry).
Release Process
- Update version number
- Don’t follow semver, simply use major and minor from H3 core and increment patch.
- Version number should be changed in root
CMakeLists.txt
. - Set
INSTALL_VERSION
to “${PROJECT_VERSION}”. - Update files (and cmake references) suffixed
--unreleased
should be renamed. - Installer
.sql
files should have@ availability
comments updated. - Update changelog by moving from
Unreleased
to a new section - Push and merge changes in
release-x.y.z
branch.
- Create a release on GitHub
- Draft new release “vX.Y.Z”
- Copy CHANGELOG.md entry into release description
- Distribute the extension on PGXN
- Run
scripts/bundle
to package the release - Upload the distribution on PGXN Manager (username:
bytesandbrains
)
- Run
- Prepare for development
- Set
INSTALL_VERSION
tounreleased
in rootCMakeLists.txt
. - Create new update files with
--unreleased
suffix. - Add them to relevant
CMakeLists.txt
files.
- Set