Versioning

When to Release

We release when:

• regularly, about monthly
• milestone goals are reached
• on special events
• we need an update of the landing page (e.g. new members etc.)

Frontend Version Numbering

Is date of planned deployment on www.permaplant.net. Should be same as the tag, except of not having an v.

E.g. if frontend version is 2026_07_24, tag would be v2026_07_24.

Backend Version Numbering

We use semantic versioning (MAJOR.MINOR.PATCH) for releases:

• MAJOR: fixed 1, we don't do changes in migrations
• MINOR: new migrations were added
• PATCH: no migrations were added

Release Process

For the detailed step-by-step release process, including:

• release preparation and version bumping
• testing and quality gates
• production deployment
• post-release activities

Please refer to the Release Issue Template located at .gitlab/issue_templates/Release.md in the repository root.

The template provides a comprehensive checklist covering all phases of the release process from initial preparation through post-release activities.