blob: bc06bc99e2ef91800b7e45b7c7fff246202e8a8b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
This is a checklist for doing Sequoia releases.
0. Starting from origin/master, create a branch XXX for the release.
1. For all 'Cargo.toml's: Bump version = "XXX".
- Only do this for non-released crates and those with changes
relative to the last released version.
2. For all 'Cargo.toml's: Bump documentation = "https://.../XXX/...".
3. For all 'Cargo.toml's: Bump intra-workspace dependencies.
4. Run 'make sanity-check-versions'.
- This simple check fails if not all versions are in sync.
5. Update dependencies and run tests.
- Run 'cargo update' to update the dependencies. If some
dependency is updated and breaks due to our MSRV, find a good
version of that dependency and select it using e.g. 'cargo
update -p backtrace --precise 0.3.46'.
- Run 'make check'.
- Run 'cargo run -p sequoia-openpgp --example statistics
--release -- ../sks-dump-*.pgp' and update
https://sequoia-pgp.org/tmp/stats.txt .
6. Make a commit with the message "Release XXX.".
- Push this to a branch on gitlab with the word 'windows' in
it, e.g. XXX-also-test-on-windows-please, and create a merge
request.
7. Make a tag vXXX with the message "Release XXX." signed with an
offline-key.
8. Make a clean clone of the repository.
9. For the following crates, cd into the directory, and do 'cargo
publish':
- buffered-reader
- openpgp
- sop
- sqv
10. In case of errors, correct them, and go back to 6.
11. Merge the branch to master by merging the merge request created in
step 6, push the tag.
12. Make a source distribution, put it on
https://sequoia-pgp.org/dist/, collect and merge signatures.
13. Regenerate docs.sequoia-pgp.org.
14. Announce the release.
- IRC
- mailing list
- web site
|
