1
1
---
2
- # Template generated by https://github.com/coreos/repo-templates; do not edit downstream
2
+ name : release checklist
3
+ about : release checklist template
4
+ title : New release for ssh-key-dir
5
+ labels : jira,kind/release
6
+ warning : |
7
+ ⚠️ Template generated by https://github.com/coreos/repo-templates; do not edit downstream
3
8
---
4
9
5
10
# Release process
@@ -94,22 +99,14 @@ Push access to the upstream repository is required in order to publish the new t
94
99
- [ ] ` git branch -d pre-release-${RELEASE_VER} release-${RELEASE_VER} `
95
100
96
101
- Fedora packaging:
97
- - [ ] update the ` rust-ssh-key-dir ` spec file in [ Fedora] ( https://src.fedoraproject.org/rpms/rust-ssh-key-dir )
98
- - bump the ` Version `
99
- - switch the ` Release ` back to ` 1%{?dist} `
100
- - remove any patches obsoleted by the new release
101
- - update changelog
102
- - [ ] run ` spectool -g -S rust-ssh-key-dir.spec `
103
- - [ ] run
` kinit [email protected] `
104
- - [ ] run ` fedpkg new-sources $(spectool -S rust-ssh-key-dir.spec | sed 's:.*/::') `
105
- - [ ] PR the changes in [ Fedora] ( https://src.fedoraproject.org/rpms/rust-ssh-key-dir )
106
- - [ ] once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f41) then push those, for example:
102
+ - [ ] Review the proposed changes in the PR submitted by Packit in [ Fedora] ( https://src.fedoraproject.org/rpms/rust-ssh-key-dir ) /pull-requests.
103
+ - [ ] once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f42) then push those, for example:
107
104
``` bash
108
105
git checkout rawhide
109
106
git pull --ff-only
110
- git checkout f41
107
+ git checkout f42
111
108
git merge --ff-only rawhide
112
- git push origin f41
109
+ git push origin f42
113
110
```
114
111
- [ ] on each of those branches run ` fedpkg build`
115
112
- [ ] once the builds have finished, submit them to [bodhi](https://bodhi.fedoraproject.org/updates/new), filling in:
@@ -125,6 +122,9 @@ Push access to the upstream repository is required in order to publish the new t
125
122
CentOS Stream 9 packaging:
126
123
- [ ] Create a ` rebase-c9s-ssh-key-dir` issue in the internal team-operations repo and follow the steps there
127
124
125
+ CentOS Stream 10 packaging:
126
+ - [ ] Create a ` rebase-c10s-ssh-key-dir` issue in the internal team-operations repo and follow the steps there
127
+
128
128
[cargo-release]: https://github.com/sunng87/cargo-release
129
129
[rustup]: https://rustup.rs/
130
130
[crates-io]: https://crates.io/
0 commit comments