Update 'Release process'
parent
da0c143ff4
commit
b9e0ded648
1 changed files with 8 additions and 8 deletions
|
@ -1,11 +1,11 @@
|
||||||
1. make sure version numbers are up to date in cargo.toml files in all subdirectories of src/ (not only the version number of the crates themselves, but also the version numbers of the dependencies to other garage crates)
|
1. make sure version numbers are up to date in cargo.toml files in all subdirectories of src/ (not only the version number of the crates themselves, but also the version numbers of the dependencies to other garage crates)
|
||||||
2. make sure cargo.lock is updated and that everything builds
|
2. make sure cargo.lock is updated and that everything builds
|
||||||
3. make a git commit
|
3. make sure cargo.nix is updated and that everything builds using nix as well
|
||||||
4. do `cargo publish` in all subdirectories, in topological sort order: util, rpc, table, model, api, web, garage
|
4. make a git commit
|
||||||
5. make a git tag
|
5. do `cargo publish` in all subdirectories, in topological sort order: db, util, rpc, table, model, api, web, garage
|
||||||
6. push the tag
|
6. make a git tag
|
||||||
7. promote the tag build
|
7. push the tag
|
||||||
8. check that the tag build went well, that release page is updated, that docker image is updated
|
8. promote the tag build
|
||||||
9. tag released image as `latest` on docker hub, do this for all archs
|
9. check that the tag build went well, that release page is updated, that docker image is updated
|
||||||
10. write release notes
|
10. write and publish release notes
|
||||||
11. celebrate
|
11. celebrate
|
Loading…
Reference in a new issue