Releasing

A PyPDFForm release starts with the following steps:

• A release issue and PR.
• A new GitHub release with auto-generated changelogs.

Once these steps are done, the CI for deployment will be triggered.

Versioning

PyPDFForm follows the conventions defined by Semantic Versioning.

Deploy process

When the GitHub release is created, it will trigger two different 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?

It depends on the changes that are currently on the master branch but have not deployed yet. Generally speaking:

• 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.