ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-04-07 10:56:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update release process: git, not darcs, etc

Browse Source
This commit is contained in:
Brian Warner 2012-01-12 23:12:57 -08:00
parent f139af3603
commit 769574f665
1 changed files with 75 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

112
docs/how_to_make_a_tahoe-lafs_release.org
View File

@ -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