cp: error on target-filename collisions, rather than overwrite

[tahoe-lafs/tahoe-lafs.git] / relnotes.txt

diff --git a/relnotes.txt b/relnotes.txt
index 446ff5fa40d9d621c8446218f925dff01c2ac1ca..36db4cf4aebfa614bb27a0291d82e44f2bb4c654 100644 (file)
--- a/relnotes.txt
+++ b/relnotes.txt
@@ -1,7 +1,7 @@
-ANNOUNCING Tahoe, the Least-Authority File System, v1.9.1
+ANNOUNCING Tahoe, the Least-Authority File System, v1.10.1
 
 The Tahoe-LAFS team is pleased to announce the immediate
-availability of version 1.9.1 of Tahoe-LAFS, an extremely
+availability of version 1.10.1 of Tahoe-LAFS, an extremely
 reliable distributed storage system. Get it here:
 
 https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst
@@ -14,12 +14,15 @@ unique security and fault-tolerance properties:
 
 https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
 
-The previous stable release of Tahoe-LAFS was v1.9.0, released
-on October 31, 2011.
+The previous stable release of Tahoe-LAFS was v1.10.0,
+released on May 1, 2013.
 
-v1.9.1 is a critical bugfix release which fixes a significant
-security issue [#1654]. See the NEWS file [1] and known_issues.rst
-[2] file for details.
+v1.10.1 is mostly a bugfix release, but also improves the
+web-based user interface, adds public-key authentication to
+the SFTP frontend, improves the behavior of "tahoe cp -r", and
+offers more control over IP address autodetection. Preliminary
+(CLI-based) OS-X packages have been added. Over 75 bugs have
+been fixed. See the NEWS file [1] for details.
 
 
 WHAT IS IT GOOD FOR?
@@ -52,7 +55,7 @@ please see the known_issues.rst file [2].)
 
 COMPATIBILITY
 
-This release is compatible with the version 1 series of
+This release should be compatible with the version 1 series of
 Tahoe-LAFS. Clients from this release can write files and
 directories in the format used by clients of all versions back
 to v1.0 (which was released March 25, 2008). Clients from this
@@ -61,7 +64,18 @@ all versions since v1.0. Servers from this release can serve
 clients of all versions back to v1.0 and clients from this
 release can use servers of all versions back to v1.0.
 
-This is the sixteenth release in the version 1 series. This
+Except for the new optional MDMF format, we have not made any
+intentional compatibility changes. However we do not yet have
+the test infrastructure to continuously verify that all new
+versions are interoperable with previous versions. We intend
+to build such an infrastructure in the future.
+
+The new Introducer protocol added in v1.10 is backwards
+compatible with older clients and introducer servers, however
+some features will be unavailable when an older node is
+involved. Please see docs/nodekeys.rst [14] for details.
+
+This is the nineteenth release in the version 1 series. This
 series of Tahoe-LAFS will be actively supported and maintained
 for the foreseeable future, and future versions of Tahoe-LAFS
 will retain the ability to read and write files compatible
@@ -125,19 +139,18 @@ Of Fame" [13].
 
 ACKNOWLEDGEMENTS
 
-This is the tenth release of Tahoe-LAFS to be created solely
-as a labor of love by volunteers. Thank you very much to the
-team of "hackers in the public interest" who make Tahoe-LAFS
-possible.
+This is the thirteenth release of Tahoe-LAFS to be created
+solely as a labor of love by volunteers. Thank you very much
+to the team of "hackers in the public interest" who make
+Tahoe-LAFS possible.
 
 Brian Warner
 on behalf of the Tahoe-LAFS team
 
-January 12, 2011
+June 15, 2015
 San Francisco, California, USA
 
 
-[#1654] https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
 [1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst
 [2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst
 [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
@@ -151,3 +164,4 @@ San Francisco, California, USA
 [11] http://atlasnetworks.us/
 [12] https://leastauthority.com/
 [13] https://tahoe-lafs.org/hacktahoelafs/
+[14] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/nodekeys.rst