You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEVELOPMENT.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,9 @@ Nothing special or automated yet. Therefore just some hints for manual testing:
18
18
19
19
1. Do proper [Testing](#testing). Continue only if everything is fine.
20
20
2. Determine the next version number. This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
21
-
3. Update the [`CHANGELOG.md`](./CHANGELOG.md). Insert a section for the new release. Do not forget the comparison link at the end of the file.
22
-
4. If everything is fine: commit the changes, tag the release and push:
21
+
3. Update the internal version variable `readonly version=` to match the new release version.
22
+
4. Update the [`CHANGELOG.md`](./CHANGELOG.md). Insert a section for the new release. Do not forget the comparison link at the end of the file.
23
+
5. If everything is fine: commit the changes, tag the release and push:
23
24
```console
24
25
git tag v<version> <commit> -m "version <version>"
25
26
git show v<version>
@@ -31,10 +32,10 @@ Nothing special or automated yet. Therefore just some hints for manual testing:
31
32
git push origin :refs/tags/v<version> # delete the old tag remotely
32
33
```
33
34
This is *only* possible if there was no [GitHub release](https://github.com/foundata/proxmox-pve-backup-usb/releases/). Use a new patch version number otherwise.
34
-
5. Use [GitHub's release feature](https://github.com/foundata/proxmox-pve-backup-usb/releases/new), select the tag you pushed and create a new release:
35
+
6. Use [GitHub's release feature](https://github.com/foundata/proxmox-pve-backup-usb/releases/new), select the tag you pushed and create a new release:
35
36
* Use `v<version>` as title
36
37
* A description is optional. In doubt, use `See CHANGELOG.md for more information about this release.`
37
-
6. Check if the GitHub API delivers the correct version as `latest`:
38
+
7. Check if the GitHub API delivers the correct version as `latest`:
0 commit comments