relnotes, docs: post-release fixups

docs/how_to_make_a_tahoe-lafs_release.org

@@ -29,15 +29,15 @@
   - [ ] upload *.asc to org ~source/downloads/
   - [ ] copy the release tarball,sigs to tahoe-lafs.org: ~source/downloads/
   - [ ] move old release out of ~source/downloads (to downloads/old/?)
-  - [ ] update Wiki front page: download link, front page news, news, old news
   - [ ] send out relnotes.txt:
     - add prefix with SHA256 of tarballs, release pubkey, git revhash
-    - GPG-sign the email
+    - GPG-sign the email with release key
     - send to tahoe-announce@tahoe-lafs.org and tahoe-dev@tahoe-lafs.org
-  - [ ] update Wiki "Doc": parade of release notes, Installation (with link
-    to tahoe-dev email)
+  - [ ] update Wiki front page: version on download link, News column
+  - [ ] update Wiki "Doc": parade of release notes (with rev of NEWS.rst)
   - [ ] close the Milestone on the trac Roadmap
   - [ ] tweet to @tahoelafs
+  - other stuff:
   - [ ] update https://tahoe-lafs.org/hacktahoelafs/
   - [ ] make an "announcement of new release" on freshmeat
   - [ ] make an "announcement of new release" on launchpad

relnotes.txt

@@ -75,7 +75,7 @@ compatible with older clients and introducer servers, however
 some features will be unavailable when an older node is
 involved. Please see docs/nodekeys.rst [14] for details.
 
-This is the nineteenth release in the version 1 series. This
+This is the twentieth release in the version 1 series. This
 series of Tahoe-LAFS will be actively supported and maintained
 for the foreseeable future, and future versions of Tahoe-LAFS
 will retain the ability to read and write files compatible