-There are two main cases where the behavior of tahoe-1.10.1 differs from that
-of the 1.10.0 release:
-
-- "cp DIRCAP/file.txt ./local/missing" , where "./local" is a directory but
- "./local/missing" does not exist. The implication is that you want tahoe to
- create a new file named "./local/missing" and fill it with the contents of
- the tahoe-side DIRCAP/file.txt. In 1.10.0, a plain "cp" would do just this,
- but "cp -r" would do "mkdir ./local/missing" and then create a file named
- "./local/missing/file.txt". In 1.10.1, both "cp" and "cp -r" create a file
- named "./local/missing".
-- "cp -r PARENTCAP/dir ./local/missing", where PARENTCAP/dir/ contains
- "file.txt", and again "./local" is a directory but "./local/missing" does
- not exist. In both 1.10.0 and 1.10.1, this first does "mkdir
- ./local/missing". In 1.10.0, it would then copy the contents of the source
- directory into the new directory, resulting in "./local/missing/file.txt".
- In 1.10.1, following the new rule of "a named directory source refers to
- the directory itself", the tool creates "./local/missing/dir/file.txt".
+There are two main cases where the behavior of Tahoe-LAFS v1.10.1 differs
+from that of the previous v1.10.0 release:
+
+- "``cp DIRCAP/file.txt ./local/missing``" , where "``./local``" is a
+ directory but "``./local/missing``" does not exist. The implication is
+ that you want Tahoe to create a new file named "``./local/missing``" and
+ fill it with the contents of the Tahoe-side ``DIRCAP/file.txt``. In
+ v1.10.0, a plain "``cp``" would do just this, but "``cp -r``" would do
+ "``mkdir ./local/missing``" and then create a file named
+ "``./local/missing/file.txt``". In v1.10.1, both "``cp``" and "``cp -r``"
+ create a file named "``./local/missing``".
+- "``cp -r PARENTCAP/dir ./local/missing``", where ``PARENTCAP/dir/``
+ contains "``file.txt``", and again "``./local``" is a directory but
+ "``./local/missing``" does not exist. In both v1.10.0 and v1.10.1, this
+ first does "``mkdir ./local/missing``". In v1.10.0, it would then copy
+ the contents of the source directory into the new directory, resulting
+ in "``./local/missing/file.txt``". In v1.10.1, following the new rule
+ of "a named directory source refers to the directory itself", the tool
+ creates "``./local/missing/dir/file.txt``".
+
+Compatibility and Dependency Updates
+------------------------------------
+
+Windows now requires Python 2.7. Unix/OS-X platforms can still use either
+Python 2.6 or 2.7, however this is probably the last release that will
+support 2.6 (it is no longer receiving security updates, and most OS
+distributions have switched to 2.7). Tahoe-LAFS now has the following
+dependencies:
+
+- Twisted >= 13.0.0
+- Nevow >= 0.11.1
+- foolscap >= 0.8.0
+- service-identity
+- characteristic >= 14.0.0
+- pyasn1 >= 0.1.4
+- pyasn1-modules >= 0.0.5
+
+On Windows, if pywin32 is not installed then the dependencies on Twisted
+and Nevow become:
+
+- Twisted >= 11.1.0, <= 12.1.0
+- Nevow >= 0.9.33, <= 0.10
+
+On all platforms, if pyOpenSSL >= 0.14 is installed, then it will be used,
+but if not then only pyOpenSSL >= 0.13, <= 0.13.1 will be built when directly
+invoking `setup.py build` or `setup.py install`.
+
+We strongly advise OS packagers to take the option of making a tahoe-lafs
+package depend on pyOpenSSL >= 0.14. In order for that to work, the following
+additional Python dependencies are needed:
+
+- cryptography
+- cffi >= 0.8
+- six >= 1.4.1
+- enum34
+- pycparser
+
+as well as libffi (for Debian/Ubuntu, the name of the needed OS package is
+`libffi6`).
+
+Tahoe-LAFS is now compatible with Setuptools version 8 and Pip version 6 or
+later, which should fix execution on Ubuntu 15.04 (it now tolerates PEP440
+semantics in dependency specifications). `#2354`_ `#2242`_
+
+Tahoe-LAFS now depends upon foolscap-0.8.0, which creates better private keys
+and certificates than previous versions. To benefit from the improvements
+(2048-bit RSA keys and SHA256-based certificates), you must re-generate your
+Tahoe nodes (which changes their TubIDs and FURLs). `#2400`_
+
+.. _`#2242`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2242
+.. _`#2354`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2354
+.. _`#2400`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2400
+
+Packaging
+---------
+
+A preliminary OS-X package, named "``tahoe-lafs-VERSION-osx.pkg``", is now
+being generated. It is a standard double-clickable installer, which creates
+``/Applications/tahoe.app`` that embeds a complete runtime tree. However
+launching the ``.app`` only brings up a notice on how to run tahoe from the
+command line. A future release may turn this into a fully-fledged application
+launcher. `#182`_ `#2393`_ `#2323`_
+
+Preliminary Docker support was added. Tahoe container images may be available
+on DockerHub. `PR#165`_ `#2419`_ `#2421`_
+
+Old and obsolete Debian packaging tools have been removed. `#2282`_
+
+.. _`#182`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/182
+.. _`#2282`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2282
+.. _`#2323`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2323
+.. _`#2393`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2393
+.. _`#2419`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2419
+.. _`#2421`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2421
+.. _`PR#165`: https://github.com/tahoe-lafs/tahoe-lafs/pull/165
+
+Minor Changes
+-------------