File: how_to_make_a_tahoe-lafs_release.org

package info (click to toggle)
tahoe-lafs 1.9.2-1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 7,240 kB
  • sloc: python: 71,758; makefile: 215; lisp: 89
file content (75 lines) | stat: -rw-r--r-- 2,988 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
* 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