docs: release notes for Tahoe-LAFS v1.8.3

This commit is contained in:
Zooko O'Whielacronx 2011-09-13 09:58:26 -07:00
parent 2025e42ec2
commit fcedf5f143
3 changed files with 117 additions and 116 deletions

View File

@ -2,93 +2,7 @@
User-Visible Changes in Tahoe-LAFS User-Visible Changes in Tahoe-LAFS
================================== ==================================
Release 1.9.0 (2011-??-??) * Release 1.8.2 (2011-01-30)
--------------------------
WORK IN PROGRESS
New Features
''''''''''''
- MDMF! #393
- blacklist #1425
- immutable-download timeline viz (#?)
- drop-upload feature (experimental) #1429
Configuration/Behavior Changes
'''''''''''''''''''''
- reject old-style (discrete) config files from <v1.3 #1385
- measure space of storage/shares/, not storage/ #1384
- 'tahoe cp xyz MUTABLE' will modify the existing mutable file instead of
creating a new one
- WUI button says "unlink" instead of "del", change docs, allow 'tahoe
unlink' #1104
Notable Bugfixes
''''''''''''''''
- 'tahoe put/cp' uploads didn't appear in history #1079
- verifier: serialize block fetches, reduce RAM footprint #1395
- make large immutable downloads faster (coalesce Share.loop() calls) #1268
Packaging Changes
'''''''''''''''''
- remove debian packaging #1454
- remove contrib/fuse #1409
- The unmaintained FUSE plugins were removed from the source tree. See
docs/frontends/FTP-and-SFTP.rst for how to use sshfs. (`#1409`_)
- replace foolscap[secure_connections] dep with one on pyopenssl #1383
- bump Twisted dependency to >=10.1
- bump zope.interface dep to <=3.6.2 or >=3.6.6 #1435
- extra-permission changes in license
- no longer need to patch Twisted for FTP, when using Twisted >= 10.1
Minor Changes
'''''''''''''
- minor: #1355, #1366, #1388, #1389, #1391, #1297, #1342, #1404, #1392,
#1412, #1344, #1345, #1347, #1334, #1274, #1438, #1120, #1359, #636, #1469,
#1149, #1441, #1503, #1510, #1507, #1505
- minor SFTP fixes: #1442, #1446
- finish .rst-ifying all docs
- shuffle configuration.rst to add Frontend section
- add man page #1420
- IServer refactoring #1363
- Nodes now emit "None" for percentiles with higher implied precision
than the number of observations can support. Older stats gatherers
will throw an exception if they gather stats from a new storage
server and it sends a "None" for a percentile. (`#1392`_)
Compatibility and Dependencies
''''''''''''''''''''''''''''''
- An incompatibility of zope.interface version 3.6.4 with Nevow has
been resolved. Tahoe-LAFS now requires one of the exact versions
v3.3.1, v3.5.3, or v3.6.1 of zope.interface. (`#1435`_)
- The Twisted dependency has been raised to version 10.1. This ensures
that we no longer require pywin32 on Windows, and that it is never
necessary to patch Twisted in order to use the FTP frontend.
(`#1274`_, `#1438`_)
.. _`#1274`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
.. _`#1392`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1392
.. _`#1409`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
.. _`#1435`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1435
.. _`#1438`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1438
** Security-related Bugfix
- Fix flaw that would allow a person who knows a storage index of a file to
delete shares of that file (#1528).
- Remove corner cases in mutable file bounds management which could expose
extra lease info or old share data (from prior versions of the mutable
file) if someone with write authority to that mutable file exercised these
corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
exploitable.) (#1528).
Release 1.8.2 (2011-01-30)
--------------------------
Compatibility and Dependencies Compatibility and Dependencies
'''''''''''''''''''''''''''''' ''''''''''''''''''''''''''''''

98
docs/quickstart.html Normal file
View File

@ -0,0 +1,98 @@
<!DOCtype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en">
<head>
<style type="text/css">
p.p1 {font-size:85%;}
p.p1 {font-style:italic;}
</style>
<title>Getting Tahoe-LAFS</title>
<link rev="made" class="mailto" href="mailto:zooko[at]zooko[dot]com">
<meta name="description" content="how to get Tahoe-LAFS">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="keywords" content="tahoe-lafs secure decentralized filesystem installation">
</head>
<body>
<h1>About Tahoe-LAFS</h1>
<p> The homepage of Tahoe-LAFS is <a href="http://tahoe-lafs.org">
http://tahoe-lafs.org</a>. There is a one-page overview at <a href="about.html">
About Tahoe-LAFS</a>.
<h1>How To Get Tahoe-LAFS</h1>
<p class=p1>This has been verified to work on Windows, Mac, OpenSolaris,
and too many flavors of Linux and of *BSD to list. It's likely to work on
other platforms.</p>
<p class=p1><strong>WARNING!</strong> There are a few third-party
libraries that Tahoe-LAFS depends on that might not be easy to set up on
your platform. If the following instructions don't Just Work, please write
to <a href="http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev">the
tahoe-dev mailing list</a> where fun, friendly, hackers will help you out!
You might also find clues in the Advanced Installation section below.</p>
<h2>Install Python</h2>
<p>Check if you already have an adequate version of Python installed by
running <cite>python --version</cite>. Python&nbsp;v2.4 (v2.4.4 or
greater), Python&nbsp;v2.5, Python&nbsp;v2.6, or Python&nbsp;v2.7 will
work. Python&nbsp;v3 does not work. On Windows, we recommend the use of
Python&nbsp;v2.6 (native, not Cygwin).</p>
<p>If you don't have one of these versions of Python installed, then
follow the instructions on
<a href="http://www.python.org/download/releases/2.6.6/">the Python
download page</a> to download and install Python&nbsp;v2.6. Make sure
that the path to the installation directory has no spaces in it (e.g. on
Windows, do not install Python in the "<tt>Program Files</tt>" directory).
</p>
<h2>Get Tahoe-LAFS</h2>
<p>Download the latest stable release, v1.8.2:</p>
<pre><a
href="http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.8.2.zip">http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.8.2.zip</a></pre>
<h2>Set Up Tahoe-LAFS</h2>
<p>Unpack the zip file and cd into the top-level directory.</p>
<p>Run <cite>python setup.py build</cite> to generate the <cite>tahoe</cite>
executable in a subdirectory of the current directory named <cite>bin</cite>.
This will download and build anything you need from various websites.</p>
<p>On Windows, the <cite>build</cite> step might tell you to open a new
Command Prompt (or, on XP and earlier, to log out and back in again).
This is needed the first time you set up Tahoe-LAFS on a particular
installation of Windows.</p>
<p>Optionally run <cite>python setup.py test</cite> to verify that it
passes all of its self-tests.</p>
<p>Run <cite>bin/tahoe --version</cite> (on Windows,
<cite>bin\tahoe --version</cite>) to verify that the executable tool prints
out the right version number.</p>
<h2>Run Tahoe-LAFS</h2>
<p>Now you are ready to deploy a decentralized filesystem. The
<cite>tahoe</cite> executable in the <cite>bin</cite> directory can
configure and launch your Tahoe-LAFS nodes.
See <a href="running.html">running.html</a> for instructions on how to do
that.</p>
<h2>Advanced Installation</h2>
<p>For optional features such as tighter integration with your operating
system's package manager, you can see the
<a href="http://tahoe-lafs.org/trac/tahoe/wiki/AdvancedInstall">AdvancedInstall</a>
wiki page. The options on that page are not necessary to use Tahoe-LAFS
and can be complicated, so we do not recommend following that page unless
you have unusual requirements for advanced optional features. For most
people, you should first follow the instructions on this page, and if that
doesn't work then ask for help by writing to
<a href="http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev">the
tahoe-dev mailing list</a>.</p>
</body>
</html>

View File

@ -1,7 +1,7 @@
ANNOUNCING Tahoe, the Least-Authority File System, v1.8.2 ANNOUNCING Tahoe, the Least-Authority File System, v1.8.3
The Tahoe-LAFS team is pleased to announce the immediate The Tahoe-LAFS team is pleased to announce the immediate
availability of version 1.8.2 of Tahoe-LAFS, an extremely availability of version 1.8.3 of Tahoe-LAFS, an extremely
reliable distributed storage system. Get it here: reliable distributed storage system. Get it here:
http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.rst http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.rst
@ -14,12 +14,11 @@ unique security and fault-tolerance properties:
http://tahoe-lafs.org/source/tahoe/trunk/docs/about.rst http://tahoe-lafs.org/source/tahoe/trunk/docs/about.rst
The previous stable release of Tahoe-LAFS was v1.8.1, which was The previous stable release of Tahoe-LAFS was v1.8.2, which was
released October 28, 2010 [1]. released January 30, 2011 [1].
v1.8.2 is a stable bugfix release, adding compatibility with v1.8.3 is a stable bugfix release which fixes a security issue. See the file
the recently-released Twisted-10.2, and correcting a number of [2] and known_issues.rst [3] file for details.
minor issues. See the NEWS.rst file [2] for details.
WHAT IS IT GOOD FOR? WHAT IS IT GOOD FOR?
@ -36,7 +35,7 @@ have built other projects on top of Tahoe-LAFS and have
integrated Tahoe-LAFS with existing systems, including integrated Tahoe-LAFS with existing systems, including
Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django,
Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and
more. See the Related Projects page on the wiki [3]. more. See the Related Projects page on the wiki [4].
We believe that strong cryptography, Free and Open Source We believe that strong cryptography, Free and Open Source
Software, erasure coding, and principled engineering practices Software, erasure coding, and principled engineering practices
@ -47,7 +46,7 @@ This software is developed under test-driven development, and
there are no known bugs or security flaws which would there are no known bugs or security flaws which would
compromise confidentiality or data integrity under recommended compromise confidentiality or data integrity under recommended
use. (For all important issues that we are currently aware of use. (For all important issues that we are currently aware of
please see the known_issues.rst file [4].) please see the known_issues.rst file [3].)
COMPATIBILITY COMPATIBILITY
@ -61,7 +60,7 @@ all versions since v1.0. Servers from this release can serve
clients of all versions back to v1.0 and clients from this clients of all versions back to v1.0 and clients from this
release can use servers of all versions back to v1.0. release can use servers of all versions back to v1.0.
This is the thirteenth release in the version 1 series. This This is the fourteenth release in the version 1 series. This
series of Tahoe-LAFS will be actively supported and maintained series of Tahoe-LAFS will be actively supported and maintained
for the foreseeable future, and future versions of Tahoe-LAFS for the foreseeable future, and future versions of Tahoe-LAFS
will retain the ability to read and write files compatible will retain the ability to read and write files compatible
@ -106,19 +105,9 @@ resources for hackers.
SPONSORSHIP SPONSORSHIP
Tahoe-LAFS was originally developed by Allmydata, Inc., a Atlas Networks has contributed several hosted servers for performance
provider of commercial backup services. After discontinuing testing. Thank you to Atlas Networks for their generous and public-spirited
funding of Tahoe-LAFS R&D in early 2009, they continued support.
to provide servers, bandwidth, small personal gifts as tokens
of appreciation, and bug reports.
Google, Inc. sponsored Tahoe-LAFS development as part of the
Google Summer of Code 2010. They awarded four sponsorships to
students from around the world to hack on Tahoe-LAFS that
summer.
Thank you to Allmydata and Google for their generous and
public-spirited support.
HACK TAHOE-LAFS! HACK TAHOE-LAFS!
@ -132,20 +121,20 @@ Of Fame" [12].
ACKNOWLEDGEMENTS ACKNOWLEDGEMENTS
This is the seventh release of Tahoe-LAFS to be created solely This is the eighth release of Tahoe-LAFS to be created solely
as a labor of love by volunteers. Thank you very much to the as a labor of love by volunteers. Thank you very much to the
team of "hackers in the public interest" who make Tahoe-LAFS team of "hackers in the public interest" who make Tahoe-LAFS
possible. possible.
Brian Warner Zooko Wilcox-O'Hearn
on behalf of the Tahoe-LAFS team on behalf of the Tahoe-LAFS team
January 30, 2011 September 13, 2011
San Francisco, California, USA Boulder, Colorado, USA
[1] http://tahoe-lafs.org/trac/tahoe/browser/relnotes.txt?rev=4865 [1] http://tahoe-lafs.org/trac/tahoe/browser/relnotes.txt?rev=4865
[2] http://tahoe-lafs.org/trac/tahoe/browser/NEWS?rev=5000 [2] http://tahoe-lafs.org/trac/tahoe/browser/NEWS.rst?rev=5000
[3] http://tahoe-lafs.org/trac/tahoe/wiki/RelatedProjects [3] http://tahoe-lafs.org/trac/tahoe/wiki/RelatedProjects
[4] http://tahoe-lafs.org/trac/tahoe/browser/docs/known_issues.rst [4] http://tahoe-lafs.org/trac/tahoe/browser/docs/known_issues.rst
[5] http://tahoe-lafs.org/trac/tahoe/browser/COPYING.GPL [5] http://tahoe-lafs.org/trac/tahoe/browser/COPYING.GPL
@ -153,6 +142,6 @@ San Francisco, California, USA
[7] http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.rst [7] http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.rst
[8] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev [8] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
[9] http://tahoe-lafs.org/trac/tahoe/roadmap [9] http://tahoe-lafs.org/trac/tahoe/roadmap
[10] http://tahoe-lafs.org/trac/tahoe/browser/CREDITS?rev=5000 [10] http://tahoe-lafs.org/trac/tahoe-lafs/browser/1.8.3/CREDITS?rev=5003
[11] http://tahoe-lafs.org/trac/tahoe/wiki/Dev [11] http://tahoe-lafs.org/trac/tahoe/wiki/Dev
[12] http://tahoe-lafs.org/hacktahoelafs/ [12] http://tahoe-lafs.org/hacktahoelafs/