--- /dev/null
+1 update doc files: relnotes.txt, CREDITS, docs/known_issues.txt, NEWS. Add release name and date to top-most item in NEWS.
+2 change docs/install.html to point to just the current tahoe-X.Y.Z.zip source code file, or else to point to a directory which contains only tahoe-X.Y.Z.* source code files
+3 darcs pull
+4 make tag
+5 make sure buildbot is green
+6 make sure other people aren't committing at that moment
+7 push tag along with some other patch to trigger buildslaves
+8 make sure buildbot is green
+9 make sure debs got built and uploaded properly
+10 make sure a sumo sdist tarball got built and uploaded properly
+11 send out relnotes.txt: tahoe-announce@lists.allmydata.org, tahoe-dev@lists.allmydata.org, p2p-hackers@lists.zooko.com, lwn@lwn.net, cap-talk@mail.eros-os.org, cryptography@metzdown.com, twisted-python@twistedmatrix.com, fuse-devel@lists.sourceforge.net, duplicity-talk@nongnu.org, news@phoronix.com, python-list@python.org, cygwin@cygwin.com, linked in cloud storage group, The Boulder Linux Users' Group, cryptopp-users@googlegroups.com, the "decentralization" group on groups.yahoo.com, andrew.orlowski@theregister.co.uk, tiddlywiki, hadoop, bzr, the cloud computing group on google, bacula mailing list, amanda?
+12 update Wiki: front page news, news, old news, parade of release notes
+13 update hacktahoe.org
+14 update "current version" information and make an "announcement of new release" on freshmeat
+15 upload to pypi with "python ./setup.py sdist upload register"
+16 update "current version" information and make an "announcement of new release" on launchpad
+17 symlink the release tarball on allmydata.org: /var/www/source/tahoe/releases/
+18 close the Milestone on the trac Roadmap
+++ /dev/null
-1 update doc files: relnotes.txt, CREDITS, docs/known_issues.txt, NEWS. Add release name and date to top-most item in NEWS.
-2 change docs/install.html to point to just the current tahoe-X.Y.Z.zip source code file, or else to point to a directory which contains only tahoe-X.Y.Z.* source code files
-3 darcs pull
-4 make tag
-5 make sure buildbot is green
-6 make sure other people aren't committing at that moment
-7 push tag along with some other patch to trigger buildslaves
-8 make sure buildbot is green
-9 make sure debs got built and uploaded properly
-10 make sure a sumo sdist tarball got built and uploaded properly
-11 send out relnotes.txt: tahoe-announce@lists.allmydata.org, tahoe-dev@lists.allmydata.org, p2p-hackers@lists.zooko.com, lwn@lwn.net, cap-talk@mail.eros-os.org, cryptography@metzdown.com, twisted-python@twistedmatrix.com, fuse-devel@lists.sourceforge.net, duplicity-talk@nongnu.org, news@phoronix.com, python-list@python.org, cygwin@cygwin.com, linked in cloud storage group, The Boulder Linux Users' Group, cryptopp-users@googlegroups.com, the "decentralization" group on groups.yahoo.com, andrew.orlowski@theregister.co.uk, tiddlywiki, hadoop, bzr, the cloud computing group on google, bacula mailing list, amanda?
-12 update Wiki: front page news, news, old news, parade of release notes
-13 update hacktahoe.org
-14 update "current version" information and make an "announcement of new release" on freshmeat
-15 upload to pypi with "python ./setup.py sdist upload register"
-16 update "current version" information and make an "announcement of new release" on launchpad
-17 symlink the release tarball on allmydata.org: /var/www/source/tahoe/releases/
-18 close the Milestone on the trac Roadmap
=== Downloading B bytes of an A-byte mutable file ===
network: A
-memory footprint: N/k*A
+memory footprint: A
notes: As currently implemented, mutable files must be downloaded in
their entirety before any part of them can be read. We are