docs: update the list of forums to announce Tahoe-LAFS too, add empty checkboxes

diff --git a/docs/how_to_make_a_tahoe-lafs_release.txt b/docs/how_to_make_a_tahoe-lafs_release.txt
index 13abcc9d6b851f980045dcb257f99fe83da12b97..3a2775bbf15cafb14c6de360aa5e01afae4fe29e 100644 (file)
--- a/docs/how_to_make_a_tahoe-lafs_release.txt
+++ b/docs/how_to_make_a_tahoe-lafs_release.txt
@@ -1,18 +1,18 @@
-1 update doc files: relnotes.txt, CREDITS, docs/known_issues.txt, NEWS. Add release name and date to top-most item in NEWS.
-2 change docs/quickstart.html to point to just the current allmydata-tahoe-X.Y.Z.zip source code file, or else to point to a directory which contains only allmydata-tahoe-X.Y.Z.* source code files
-3 darcs pull
-4 make tag
-5 make sure buildbot is green
-6 make sure other people aren't committing at that moment
-7 push tag along with some other patch to trigger buildslaves
-8 make sure buildbot is green
-9 make sure debs got built and uploaded properly
-10 make sure a sumo sdist tarball got built and uploaded properly
-11 symlink the release tarball on allmydata.org: /var/www/source/tahoe/releases/
-12 update Wiki: front page news, news, old news, parade of release notes
-13 send out relnotes.txt: tahoe-announce@lists.allmydata.org, tahoe-dev@lists.allmydata.org, p2p-hackers@lists.zooko.com, lwn@lwn.net, cap-talk@mail.eros-os.org, cryptography@metzdown.com, twisted-python@twistedmatrix.com, fuse-devel@lists.sourceforge.net, fuse-sshfs@lists.sourceforge.net, duplicity-talk@nongnu.org, news@phoronix.com, python-list@python.org, cygwin@cygwin.com, linked in cloud storage group, The Boulder Linux Users' Group, cryptopp-users@googlegroups.com, the "decentralization" group on groups.yahoo.com, andrew.orlowski@theregister.co.uk, tiddlywiki, hadoop, bzr, the cloud computing group on google, bacula mailing list, amanda?
-14 update hacktahoe.org
-15 update "current version" information and make an "announcement of new release" on freshmeat
-16 upload to pypi with "python ./setup.py sdist upload register"
-17 update "current version" information and make an "announcement of new release" on launchpad
-18 close the Milestone on the trac Roadmap
+[ ] 1 update doc files: relnotes.txt, CREDITS, docs/known_issues.txt, NEWS. Add release name and date to top-most item in NEWS.
+[ ] 2 change docs/quickstart.html to point to just the current allmydata-tahoe-X.Y.Z.zip source code file, or else to point to a directory which contains only allmydata-tahoe-X.Y.Z.* source code files
+[ ] 3 darcs pull
+[ ] 4 make tag
+[ ] 5 make sure buildbot is green
+[ ] 6 make sure other people aren't committing at that moment
+[ ] 7 push tag along with some other patch to trigger buildslaves
+[ ] 8 make sure buildbot is green
+[ ] 9 make sure debs got built and uploaded properly
+[ ] 10 make sure a sumo sdist tarball got built and uploaded properly
+[ ] 11 symlink the release tarball on tahoe-lafs.org: /var/www/source/tahoe-lafs/releases/
+[ ] 12 update Wiki: front page news, news, old news, parade of release notes
+[ ] 13 send out relnotes.txt: [ ] tahoe-announce@tahoe-lafs.org, [ ] tahoe-dev@tahoe-lafs.org, [ ] p2p-hackers@lists.zooko.com, [ ] lwn@lwn.net, [ ] cap-talk@mail.eros-os.org, [ ] cryptography@metzdown.com & cryptography@randombit.net, [ ] twisted-python@twistedmatrix.com, [ ] owncloud@kde.org, [ ] the "decentralization" group on groups.yahoo.com, [ ] pycrypto mailing list, -> fuse-devel@lists.sourceforge.net, -> fuse-sshfs@lists.sourceforge.net, [ ] duplicity-talk@nongnu.org, [ ] news@phoronix.com, [ ] python-list@python.org, -> cygwin@cygwin.com, [ ] The Boulder Linux Users' Group, [ ] The Boulder Hackerspace mailing list, [ ] cryptopp-users@googlegroups.com, [ ] tiddlywiki, [ ] hadoop, [ ] bzr, [ ] mercurial
+[ ] 14 update hacktahoe.org
+[ ] 15 make an "announcement of new release" on freshmeat
+[ ] 16 upload to pypi with "python ./setup.py sdist upload register"
+[ ] 17 update "current version" information and make an "announcement of new release" on launchpad
+[ ] 18 close the Milestone on the trac Roadmap