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 suffixed
--unreleasedshould be renamed. - Installer
.sqlfiles should have@ availabilitycomments updated. - Update changelog by moving from
Unreleasedto a new section - Push and merge changes in
release-x.y.zbranch.
- 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/bundleto package the release - Upload the distribution on PGXN Manager (username:
bytesandbrains)
- Run
- Prepare for development
- Reset version numbers in root
CMakeLists.txtandMETA.jsontounreleased - Create new update files with
--unreleasedsuffix.
- Reset version numbers in root