Branching workflow
Please do not translate this page.
This branch is where all other feature branches are merged into.
Merge to this branch is allowed only by a project owner or coordinator and always via pull request.
NOTE: merges into this branch must not be fast-forwards.
Create a branch for anything you want to implement. Later merge to master will be authorized by a project owner or coordinator via pull request.
Created when a new version is about to be released. Always forked from one point in master It will advance with master for changes that should go into a new release (release bump, changelog updates, last minute fixes). Release branches will also be used for hotfixes.
Once the tag is created and the release process is complete, this branch must be merged to master and then deleted.
NOTE: code-related commits to this branch are allowed only for last minute fixes and eventually merged to master.
Latest stable version (that is, released to non-beta publishing channels). It will always point to the latest release tag.
Every release is tagged using semantic versioning.
- Desktop client
- FAQ (de, sr, es,)
- The personal key (de, sr, es)
- Export personal key to another device (de, it, nl, sr, es)
- Android client permissions (de, nl, sr, es)