Releasing

The PyPDFForm release process involves these initial steps:

1. A version bump commit that runs black and isort on the codebase.
2. A new GitHub release with auto-generated changelogs.

These steps trigger the deployment CI.

Versioning

PyPDFForm follows the conventions defined by Semantic Versioning.

Deploy process

A GitHub release triggers two CIs:

• Deploy, which will create the distribution and upload it to PyPI.
• Deploy Docs, which will tear down and rebuild the GitHub page where the doc site is hosted.

When are releases done?

Release timing depends on changes pending deployment on the master branch. Generally:

• Serious bugs are usually released immediately after they are fixed.
• New features can usually wait and are released on a weekly basis.
• Trivial changes are usually bundled with other changes and can wait indefinitely.