From 769574f66532e8e6e106c58a75dd174d04a131ca Mon Sep 17 00:00:00 2001 From: Brian Warner <warner@lothar.com> Date: Thu, 12 Jan 2012 23:12:57 -0800 Subject: [PATCH] update release process: git, not darcs, etc --- docs/how_to_make_a_tahoe-lafs_release.org | 112 +++++++++++++++------- 1 file changed, 75 insertions(+), 37 deletions(-) diff --git a/docs/how_to_make_a_tahoe-lafs_release.org b/docs/how_to_make_a_tahoe-lafs_release.org index 19f10054..c98af548 100644 --- a/docs/how_to_make_a_tahoe-lafs_release.org +++ b/docs/how_to_make_a_tahoe-lafs_release.org @@ -1,37 +1,75 @@ -â 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] + - [ ] update doc files + - 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 + - [ ] git pull + - [ ] git tag 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 along with some other documentation-only patch (typically to + relnotes.txt) to trigger buildslaves + - git push --tags official; git push official + - 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 + - [ ] send out relnotes.txt to: + - tahoe-announce@tahoe-lafs.org + - tahoe-dev@tahoe-lafs.org + - [ ] update https://tahoe-lafs.org/hacktahoelafs/ + - [ ] 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 + - 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 -- 2.45.2