-☐ 1 update doc files: `<../relnotes.txt>`_, `<../CREDITS>`_, `<known_issues.rst>`_, `<../NEWS.rst>`_. Add release name and date to top-most item in NEWS.
-
-☐ 2 change `<quickstart.rst>`_ 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 build locally to make sure the release is reporting itself as the intended version
-
-☐ 6 make sure buildbot is green
-
-☐ 7 make sure other people aren't committing at that moment
-
-☐ 8 push tag along with some other documentation-only patch (typically to relnotes.txt) to trigger buildslaves
-
-☐ 9 make sure buildbot is green
-
-☐ 10 make sure debs got built and uploaded properly
-
-☐ 11 make sure a sumo sdist tarball got built and uploaded properly
-
-☐ 12 symlink the release tarball on tahoe-lafs.org: /var/www/source/tahoe-lafs/releases/
-
-☐ 13 update Wiki: front page news, news, old news, parade of release notes
-
-☐ 14 send out relnotes.txt: ☐ tahoe-announce@tahoe-lafs.org, ☐ tahoe-dev@tahoe-lafs.org, ☐ p2p-hackers@lists.zooko.com, ☐ lwn@lwn.net, ☐ a Google+ page, ☐ cap-talk@mail.eros-os.org, ☐ cryptography@metzdown.com, ☐ cryptography@randombit.net, ☐ twisted-python@twistedmatrix.com, ☐ owncloud@kde.org, ☐ liberationtech@lists.stanford.edu, ☐ 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, ☐ hdfs-dev@hadoop.apache.org, ☐ bzr, ☐ mercurial, ☐ http://listcultures.org/pipermail/p2presearch_listcultures.org/ , deltacloud, libcloud, ☐ swift@lists.launchpad.net, ☐ stephen@fosketts.net, ☐ Chris Mellor of The Register, ☐ nosql@mypopescu.com, ☐ The H Open, fans/customers of cleversafe, fans/customers of bitcasa, fans/customers of wuala, fans/customers of spideroak
-
-☐ 15 update `<https://tahoe-lafs.org/hacktahoelafs/>`_
-
-☐ 16 make an "announcement of new release" on freshmeat
-
-☐ 17 upload to pypi with "python ./setup.py sdist upload register"
-
-☐ 18 make an "announcement of new release" on launchpad
-
-☐ 19 close the Milestone on the trac Roadmap
+* Tahoe Release Checklist [0/19]
+ - [ ] NEWS.rst: summarize user-visible changes, aim for one page of text
+ - [ ] update doc files
+ - NEWS.rst: Add final release name and date to top-most item in NEWS.
+ - relnotes.txt
+ - CREDITS
+ - docs/known_issues.rst
+ - [ ] change docs/quickstart.rst 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
+ - [ ] git pull
+ - [ ] git tag -s -u 68666A7A allmydata-tahoe-X.Y.Z
+ - produces a "signed tag"
+ - tag body: allmydata-tahoe-X.Y.Z
+ - [ ] build locally to make sure the release is reporting itself as the
+ intended version
+ - [ ] make sure buildbot is green
+ - [ ] make sure other people aren't committing at that moment
+ - [ ] push tag to trigger buildslaves. Making a code change is no longer
+ necessary
+ - git push official master TAGNAME
+ - that will build tarballs
+ - [ ] make sure buildbot is green
+ - [ ] make sure a sumo sdist tarball got built and uploaded properly
+ - [ ] download tarballs, sign with "gpg -ba -u 68666a7a TAR", upload *.asc
+ - [ ] symlink the release tarball on tahoe-lafs.org:
+ /var/www/source/tahoe-lafs/releases/
+ - [ ] update Wiki: front page news, news, old news, parade of release
+ notes ("Doc"), Installation
+ - [ ] send out relnotes.txt:
+ - modify to include hashes of tarballs, git revision
+ - GPG-sign the email
+ - send to tahoe-announce@tahoe-lafs.org and tahoe-dev@tahoe-lafs.org
+ - [ ] update https://tahoe-lafs.org/hacktahoelafs/
+ - [ ] update pypi:
+ - python setup.py register
+ - login to pypi
+ - manually upload .tar.gz tarball and .asc signature (so they match the
+ ones on tahoe-lafs.org), or use https://pypi.python.org/pypi/twine and
+ run "twine upload *.tar.gz *.asc"
+ - [ ] close the Milestone on the trac Roadmap
+ - [ ] make an "announcement of new release" on freshmeat
+ - [ ] make an "announcement of new release" on launchpad
+ - [ ] send out relnotes.txt to:
+ - p2p-hackers@lists.zooko.com
+ - lwn@lwn.net
+ - a Google+ page
+ - cap-talk@mail.eros-os.org
+ - cryptography@metzdown.com
+ - cryptography@randombit.net
+ - twisted-python@twistedmatrix.com
+ - owncloud@kde.org
+ - liberationtech@lists.stanford.edu
+ - 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
+ - hdfs-dev@hadoop.apache.org
+ - bzr
+ - mercurial
+ - http://listcultures.org/pipermail/p2presearch_listcultures.org/
+ - deltacloud
+ - libcloud
+ - swift@lists.launchpad.net
+ - stephen@fosketts.net
+ - Chris Mellor of The Register
+ - nosql@mypopescu.com
+ - The H Open
+ - fans/customers of cleversafe
+ - fans/customers of bitcasa
+ - fans/customers of wuala
+ - fans/customers of spideroak
projects / tahoe-lafs / tahoe-lafs.git / blobdiff