39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
-
+
-
+
-
+
+
+
+
+
+
+
+
+
|
1. `for i in f38 f39 epel8 epel9; do git checkout $i && git merge rawhide; done`
1. `git push`
1. `for i in rawhide f38 f39 epel8 epel9; do git checkout $i && fedpkg build --nowait; done`
1. Wait for the builds to be done, then create the updates on [Bodhi](https://bodhi.fedoraproject.org/). Set the Karma required to 1.
### Homebrew
1. Edit the [Formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/o/objfw.rb) on GitHub to increase the version and update the hash.
1. Edit the [Formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/o/objfw.rb) to increase the version and update the hash.
1. Commit with the message `objfw ${version}` and create a draft pull request. This will trigger CI.
1. Once CI passed, click on `Ready for review`.
## MSYS2
### MSYS2
1. Edit the [`PKGBUILD`](https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-objfw/PKGBUILD) file to increase the version and update the hash.
1. Commit with the message `objfw: Update to ${version}` and create a draft pull request. This will trigger CI.
1. Once CI passed, click on `Ready for review`.
## OpenIndiana
### OpenIndiana
1. Edit the [`Makefile`](https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/library/objfw/Makefile) to increase the version and update the hash.
1. If a library minor increased, the `*.p5m` files need to be changed as well.
1. Commit with the message `library/objfw: update to ${version}` and create a draft pull request. This will trigger CI.
1. Once CI passed, click on `Ready for review`.
### 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`.
|