ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-06-01 15:20:55 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update release how-to to be closer to current reality

Browse Source
This commit is contained in:
Brian Warner 2013-05-01 15:24:24 -07:00
parent 397a95e827
commit a3891d98d7
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/how_to_make_a_tahoe-lafs_release.org
View File

@ -1,9 +1,10 @@
* Tahoe Release Checklist [0/19] * Tahoe Release Checklist [0/19]
- [ ] NEWS.rst: summarize user-visible changes, aim for one page of text
- [ ] update doc files - [ ] update doc files
- NEWS.rst: Add final release name and date to top-most item in NEWS.
- relnotes.txt - relnotes.txt
- CREDITS - CREDITS
- docs/known_issues.rst - 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 - [ ] 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 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 directory which contains only allmydata-tahoe-X.Y.Z.* source code files
@ -13,9 +14,9 @@
intended version intended version
- [ ] make sure buildbot is green - [ ] make sure buildbot is green
- [ ] make sure other people aren't committing at that moment - [ ] make sure other people aren't committing at that moment
- [ ] push tag along with some other documentation-only patch (typically to - [ ] push tag to trigger buildslaves. Making a code change is no longer
relnotes.txt) to trigger buildslaves necessary
- git push --tags official; git push official - git push official master TAGNAME
- that will build tarballs - that will build tarballs
- [ ] make sure buildbot is green - [ ] make sure buildbot is green
- [ ] make sure a sumo sdist tarball got built and uploaded properly - [ ] make sure a sumo sdist tarball got built and uploaded properly
@ -23,19 +24,19 @@
- [ ] symlink the release tarball on tahoe-lafs.org: - [ ] symlink the release tarball on tahoe-lafs.org:
/var/www/source/tahoe-lafs/releases/ /var/www/source/tahoe-lafs/releases/
- [ ] update Wiki: front page news, news, old news, parade of release notes - [ ] update Wiki: front page news, news, old news, parade of release notes
- [ ] send out relnotes.txt to: - [ ] send out relnotes.txt:
- tahoe-announce@tahoe-lafs.org - modify to include hashes of tarballs, git revision
- tahoe-dev@tahoe-lafs.org - GPG-sign the email
- send to tahoe-announce@tahoe-lafs.org and tahoe-dev@tahoe-lafs.org
- [ ] update https://tahoe-lafs.org/hacktahoelafs/ - [ ] update https://tahoe-lafs.org/hacktahoelafs/
- [ ] make an "announcement of new release" on freshmeat - [ ] update pypi:
- [ ] upload to pypi with "python ./setup.py sdist upload register" - python setup.py register
- currently broken (with git). And we want signed tarballs, and we want - login to pypi
the tarballs to match the ones on tahoe-lafs.org. So instead do this: - manually upload .tar.gz tarball and .asc signature (so they match the
- [ ] login to pypi ones on tahoe-lafs.org)
- [ ] from Edit, add new release
- [ ] upload .tar.gz, .asc
- [ ] make an "announcement of new release" on launchpad
- [ ] close the Milestone on the trac Roadmap - [ ] 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: - [ ] send out relnotes.txt to:
- p2p-hackers@lists.zooko.com - p2p-hackers@lists.zooko.com
- lwn@lwn.net - lwn@lwn.net