From: Brian Warner Date: Wed, 1 May 2013 22:24:24 +0000 (-0700) Subject: update release how-to to be closer to current reality X-Git-Tag: allmydata-tahoe-1.10.1a1~250 X-Git-Url: https://git.rkrishnan.org/components/com_hotproperty/css/@manifest?a=commitdiff_plain;h=a3891d98d75ea67b6319fafcdd86a74e098faac8;p=tahoe-lafs%2Ftahoe-lafs.git update release how-to to be closer to current reality --- diff --git a/docs/how_to_make_a_tahoe-lafs_release.org b/docs/how_to_make_a_tahoe-lafs_release.org index c98af548..c3aae9d3 100644 --- a/docs/how_to_make_a_tahoe-lafs_release.org +++ b/docs/how_to_make_a_tahoe-lafs_release.org @@ -1,9 +1,10 @@ * 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 - - NEWS.rst: Add release name and date to top-most item in NEWS. - [ ] 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 @@ -13,9 +14,9 @@ intended version - [ ] make sure buildbot is green - [ ] make sure other people aren't committing at that moment - - [ ] push tag along with some other documentation-only patch (typically to - relnotes.txt) to trigger buildslaves - - git push --tags official; git push official + - [ ] 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 @@ -23,19 +24,19 @@ - [ ] 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 - - [ ] send out relnotes.txt to: - - tahoe-announce@tahoe-lafs.org - - tahoe-dev@tahoe-lafs.org + - [ ] 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) + - [ ] close the Milestone on the trac Roadmap - [ ] make an "announcement of new release" on freshmeat - - [ ] upload to pypi with "python ./setup.py sdist upload register" - - currently broken (with git). And we want signed tarballs, and we want - the tarballs to match the ones on tahoe-lafs.org. So instead do this: - - [ ] login to pypi - - [ ] from Edit, add new release - - [ ] upload .tar.gz, .asc - [ ] make an "announcement of new release" on launchpad - - [ ] close the Milestone on the trac Roadmap - [ ] send out relnotes.txt to: - p2p-hackers@lists.zooko.com - lwn@lwn.net