User-Visible Changes in Tahoe-LAFS
==================================
-Release 1.9.2a1 (2012-06-23)
+Release 1.9.2 (2012-07-03)
----------------------------
Notable Bugfixes
''''''''''''''''
-- Several regressions in support for reading (`#1636`, `#1670`), writing
- (`#1749`), verifying (`#1628`) and repairing (`#1655`, `#1669`, `#1676`,
- `#1689`) mutable files have been fixed.
+- Several regressions in support for reading (`#1636`_), writing/modifying
+ (`#1670`_, `#1749`_), verifying (`#1628`_) and repairing (`#1655`_, `#1669`_,
+ `#1676`_, `#1689`_) mutable files have been fixed.
- FTP can now list directories containing mutable files, although it
- still does not support reading or writing mutable files. (`#680`)
+ still does not support reading or writing mutable files. (`#680`_)
- The FTP frontend would previously show Jan 1 1970 for all timestamps;
now it shows the correct modification time of the directory entry.
- (`#1688`)
+ (`#1688`_)
- If a node is configured to report incidents to a log gatherer, but the
gatherer is offline when some incidents occur, it would previously not
- "catch up" with those incidents as intended. (`#1725`)
-- OpenBSD 5 is now supported. (`#1584`)
+ "catch up" with those incidents as intended. (`#1725`_)
+- OpenBSD 5 is now supported. (`#1584`_)
+- The ``count-good-share-hosts`` field of file check results is now
+ computed correctly. (`#1115`_)
-Configuration/Behaviour Changes
-'''''''''''''''''''''''''''''''
+Configuration/Behavior Changes
+''''''''''''''''''''''''''''''
- The capability of the upload directory for the drop-upload frontend
is now specified in the file ``private/drop_upload_dircap`` under
the gateway's node directory, rather than in its ``tahoe.cfg``.
- (`#1593`)
+ (`#1593`_)
Packaging Changes
'''''''''''''''''
- Tahoe-LAFS can be built correctly from a git repository as well as
from darcs.
-- Versions 2.0.1 and 2.4 of PyCrypto are excluded. (`#1631`, `#1574`)
+
+Compatibility and Dependencies
+''''''''''''''''''''''''''''''
+
+- foolscap >= 0.6.3 is required, in order to make Tahoe-LAFS compatible
+ with Twisted >= 11.1.0. (`#1788`_)
+- Versions 2.0.1 and 2.4 of PyCrypto are excluded. (`#1631`_, `#1574`_)
.. _`#680`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/680
+.. _`#1115`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1115
.. _`#1574`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1574
.. _`#1584`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1584
.. _`#1593`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1593
.. _`#1689`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1689
.. _`#1725`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1725
.. _`#1749`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1749
+.. _`#1788`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1788
Release 1.9.1 (2012-01-12)
versions, and because the algorithm does not yet meet memory-usage goals.
Enable it with ``--format=MDMF`` in the CLI (``tahoe put`` and ``tahoe
mkdir``), or the "format" radioboxes in the web interface. See
- `<docs/specifications/mutable.rst>`_ for more details (`#393`_, `#1507`_)
+ `<docs/specifications/mutable.rst>`__ for more details (`#393`_, `#1507`_)
- A "blacklist" feature allows blocking access to specific files through
a particular gateway. See the "Access Blacklist" section of
- `<docs/configuration.rst>`_ for more details. (`#1425`_)
+ `<docs/configuration.rst>`__ for more details. (`#1425`_)
- A "drop-upload" feature has been added, which allows you to upload
files to a Tahoe-LAFS directory just by writing them to a local
directory. This feature is experimental and should not be relied on
to store the only copy of valuable data. It is currently available
- only on Linux. See `<docs/frontends/drop-upload.rst>`_ for documentation.
+ only on Linux. See `<docs/frontends/drop-upload.rst>`__ for documentation.
(`#1429`_)
- The timeline of immutable downloads can be viewed using a zoomable and
pannable JavaScript-based visualization. This is accessed using the
.. _`#1268`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1268
.. _`#1274`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
.. _`#1304`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304
-.. _`#1355`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1355
.. _`#1383`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383
.. _`#1384`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1384
.. _`#1385`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385
-.. _`#1388`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1388
.. _`#1391`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1391
-.. _`#1392`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1392
.. _`#1395`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1395
.. _`#1409`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
.. _`#1420`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1420
- "tahoe --version" should now report correct values in situations
where 1.8.1 might have been wrong (`#1287`_)
-.. _`#174`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
.. _`#1208`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1208
.. _`#1282`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1282
.. _`#1286`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1286
- pycrypto 2.2 is excluded due to a bug
.. _`#188`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/188
-.. _`#287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
.. _`#288`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/288
.. _`#448`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/448
.. _`#685`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/685
.. _`#741`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/741
.. _`#760`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/760
.. _`#761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/761
-.. _`#768`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/768
.. _`#773`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/773
.. _`#786`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/786
.. _`#828`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/828
projects / tahoe-lafs / tahoe-lafs.git / blobdiff