From: Brian Warner <warner@lothar.com> Date: Fri, 13 Jan 2012 07:01:53 +0000 (-0800) Subject: prepare to Org-ify how_to_make_a_tahoe-lafs_release: rename the file X-Git-Url: https://git.rkrishnan.org/components/CLI.txt?a=commitdiff_plain;h=f139af36038ba405947d510ee55fe819d9da0aac;p=tahoe-lafs%2Ftahoe-lafs.git prepare to Org-ify how_to_make_a_tahoe-lafs_release: rename the file --- diff --git a/docs/how_to_make_a_tahoe-lafs_release.org b/docs/how_to_make_a_tahoe-lafs_release.org new file mode 100644 index 00000000..19f10054 --- /dev/null +++ b/docs/how_to_make_a_tahoe-lafs_release.org @@ -0,0 +1,37 @@ +â 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 diff --git a/docs/how_to_make_a_tahoe-lafs_release.rst b/docs/how_to_make_a_tahoe-lafs_release.rst deleted file mode 100644 index 19f10054..00000000 --- a/docs/how_to_make_a_tahoe-lafs_release.rst +++ /dev/null @@ -1,37 +0,0 @@ -â 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