ObjFW  Changes To Release process

Changes to "Release process" between 2024-01-17 21:30:22 and 2024-01-20 22:08:14

23
24
25
26
27
28
29

30
31
32
33
34
35
36
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37







+








In `devel/objfw`:

1. Edit `Makefile` to increase version.
1. Run `make makesum` to update `distinfo`. Check it is correct.
1. Run `make package`.
1. Run `make update-PLIST >PLIST` to update the `PLIST`. Look at the diff and fix any custom `PLIST` entries that this reverted. Pay attention to what is already in the other `PLIST.*` files!
1. Commit and run `make cce`.

### Fedora

1. Make sure to be on rawhide.
1. Increase version in  `objfw.spec` and `git add` it.
1. Download the tarball and signature via `spectool -g objfw.spec`.
1. `fedpkg upload` both `objfw-${version}.tar.gz` and `objfw-${version}.tar.gz.sig`.
63
64
65
66
67
68
69










64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80







+
+
+
+
+
+
+
+
+
+
### Alpine Linux

1. Edit the [`APKBUILD`](https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/objfw/APKBUILD?ref_type=heads) to increase the version and update the file name and hash.
1. Commit with the message `community/objfw: upgrade to ${version}` and create a draft pull request. This will trigger CI.
1. (Optional) Manually trigger the RISC-V build.
1. Once CI passed, click on `Mark as ready`.
1. Only for bug fix-only releases: Repeat the same for every stable branch, but prefix the commit message with the branch, e.g. `[3.19] community/objfw: upgrade to 1.0.6`.

### Haiku

In `dev-libs/objfw`:

1. Rename the recipe file to the new version.
1. Update the hash.
1. Update the library versions as necessary.
1. Run `haikuporter objfw_x86` (for gcc2h) or `haikuporter objfw`.
1. Commit & push.