add release steps to readme

README.md

@@ -279,8 +279,9 @@ You have earned: 2400 USD
 
 * timetrap is [hard to install](https://github.com/samg/timetrap/issues/176),
   hard to keep [updated](https://github.com/samg/timetrap/issues/174) (because
-  of ruby). Once this tool is finished you can get (or build) a binary, put it
-  somewhere, and it will just work forever in that machine. I'm bundling sqlite.
+  of ruby). With tiempo you can get (or build) a binary, put it somewhere in
+  your `PATH`, and it will just work forever in that machine. I'm bundling
+  sqlite.
 * timetrap is slow (no way around it, because of ruby), some commands take up to
   a second. Tiempo always feels snappy.
 * needed major refactor to fix the timezone problem (in a language I'm not
@@ -293,10 +294,11 @@ You have earned: 2400 USD
 
 * Columns in the output are always aligned.
 * Fixed some input inconsistencies.
-* cli interface is easier to discover (ask -h for any sub-command)
-* end times are printed with +1d to indicate that the activity ended the next
+* CLI interface is easier to discover (ask -h for any sub-command)
+* End times are printed with +1d to indicate that the activity ended the next
   day in the 'text' formatter.
-* solved some old issues in timetrap.
+* Solved some old issues in timetrap.
+* Added new features!
 
 ## How to build
 
@@ -363,3 +365,13 @@ formatted as
 To [timetrap](https://github.com/samg/timetrap) for existing, to
 [samg](https://github.com/samg) for creating it. It is the tool I was looking
 for and whose design I took as reference, keeping compatibility when possible.
+
+## Release checklist
+
+(mostly to remind myself)
+
+* [ ] Ensure tests pass and that clippy doesn't complain
+* [ ] Create an entry in `CHANGELOG.md` with the target version
+* [ ] run `vbump`
+* [ ] push commits and tags
+* [ ] wait for release