... | ... | @@ -2,7 +2,7 @@ In order to create a new release, a few tasks need to be fulfilled. We have a sc |
|
|
|
|
|
## Compile the changelog
|
|
|
|
|
|
We use Towncrier to manage our changelog. Each closed issue should have a corresponding entry in the changes/changelog.d folder. Before releaseing the application, the changelog needs to be compiled:
|
|
|
We use Towncrier to manage our changelog. Each closed issue should have a corresponding entry in the `changes/changelog.d` folder. Before releaseing the application, the changelog needs to be compiled:
|
|
|
|
|
|
`towncrier build --version <version>`
|
|
|
|
... | ... | @@ -36,3 +36,7 @@ Result: 1.2.3-fdroid |
|
|
## Tag the application
|
|
|
|
|
|
Create an (annotated) tag named after the original version number and push the tag. A release build will automatically be triggered for a new tag.
|
|
|
|
|
|
## Automation
|
|
|
|
|
|
There's a script `create-release.sh` in the `dist/` folder. This script implements the process described above. Please use it instead of manually releasing the application. |
|
|
\ No newline at end of file |