summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Cargo.lock2
-rw-r--r--Cargo.toml4
-rw-r--r--RELEASE.md27
3 files changed, 32 insertions, 1 deletions
diff --git a/Cargo.lock b/Cargo.lock
index 1b1bcd6..0e628a0 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -516,7 +516,7 @@ dependencies = [
[[package]]
name = "vmadm"
-version = "0.1.0"
+version = "0.2.0"
dependencies = [
"anyhow",
"bytesize",
diff --git a/Cargo.toml b/Cargo.toml
index c09cb7d..8da5764 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -3,6 +3,10 @@ name = "vmadm"
version = "0.2.0"
authors = ["Lars Wirzenius <liw@liw.fi>"]
edition = "2018"
+license = "GPL-3.0-or-later"
+description = "Administer virtual machines in local libvirt"
+homepage = "https://vmadm.liw.fi/"
+repository = "https://gitlab.com/larswirzenius/vmadm"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
diff --git a/RELEASE.md b/RELEASE.md
new file mode 100644
index 0000000..071ead3
--- /dev/null
+++ b/RELEASE.md
@@ -0,0 +1,27 @@
+# Release process for vmadm
+
+* Land any changes that are in progress.
+* Make sure `./check` runs successfully.
+* Create a branch for making changes during release.
+* Update `NEWS` to cover all user-visible changes.
+* Choose new version number and update it in the relevant places.
+ - `NEWS`
+ - `Cargo.toml`
+ - `debian/changelog`
+* Commit version number changes.
+* Create a release tag: `git tag -sam "Release X.Y.Z of vmadm" vX.Y.Z`
+* Update the version number by appending `+git` to it, in all the same
+ places, except `Cargo.toml`.
+* Commit version number changes.
+* Push release branch to `gitlab.com`, create a merge request, merge it.
+* Change to the `main` branch locally, pull from `gitlab.com`.
+* Push `main` branch to `git.liw.fi` so that CI builds things.
+ - wait for that to happen
+* Push tags to `git.liw.fi` so that CI builds release.
+ - verify that it does
+* Push tags to `gitlab.com` so they're there.
+* Publish to `crates.io` with `cargo publish` after CI has built release.
+
+If there's a problem after the push of the release branch to
+`gitlab.com`, fix it, and then re-start release process from the
+beginning.