50 lines
794 B
Markdown
50 lines
794 B
Markdown
# Release Process
|
|
|
|
## Branches
|
|
|
|
Recommended Gitea layout:
|
|
|
|
- `main`: stable released source code
|
|
- `dev`: active development work
|
|
|
|
Release builds should come from `main`.
|
|
|
|
## Version Numbers
|
|
|
|
Use semantic versioning:
|
|
|
|
```text
|
|
MAJOR.MINOR.PATCH
|
|
```
|
|
|
|
Examples:
|
|
|
|
- `1.0.0`: first stable release
|
|
- `1.0.1`: bug fix
|
|
- `1.0.2`: tested feature and polish release
|
|
- `1.1.0`: new feature
|
|
|
|
Update version fields in:
|
|
|
|
```text
|
|
TaskbarLauncher.csproj
|
|
```
|
|
|
|
## Publish to Gitea
|
|
|
|
1. Commit all source changes.
|
|
2. Build the release zip locally.
|
|
3. Merge `dev` into `main`.
|
|
4. Tag the release:
|
|
|
|
```powershell
|
|
git tag v1.0.2
|
|
git push origin main
|
|
git push origin v1.0.2
|
|
```
|
|
|
|
5. In Gitea, create a release from the tag.
|
|
6. Upload the release zip.
|
|
|
|
Older releases stay available through Gitea Releases and Git tags.
|