Skip to content

Document release process  #434

@tomasaschan

Description

@tomasaschan

I did the last release (v1.0.6) but I've already forgotten how and I can't find it documented anywhere.

Since there are a few things that need to happen (eg generate release notes, push a tag, publish a release), and the project is now maintained by a loosely formed group of volunteers, it'd be useful to have a small document somewhere that explains how to do it - that lowers the threshold to create a new release, which then helps ensuring we don't sit with a bunch of features merged but unreleased.

This issue is a reminder to myself to create such documentation, if nobody gets to it before me.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions