-ANNOUNCING Tahoe, the Least-Authority File System, v1.9.0
+ANNOUNCING Tahoe, the Least-Authority File System, v1.9.2
The Tahoe-LAFS team is pleased to announce the immediate
-availability of version 1.9.0 of Tahoe-LAFS, an extremely
+availability of version 1.9.2 of Tahoe-LAFS, an extremely
reliable distributed storage system. Get it here:
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
-The previous stable release of Tahoe-LAFS was v1.8.3, which was
-released September 13, 2011.
+The previous stable release of Tahoe-LAFS was v1.9.1, released
+on January 12, 2012.
-v1.9.0 offers a new mutable-file format (more efficient for
-large files), a file-blacklisting feature, and a new
-"drop-upload" feature. See the NEWS file [3] and
-known_issues.rst [4] file for details.
+v1.9.2 is a bugfix release that primarily fixes regressions
+in mutable file support. See the NEWS file [1] for details.
WHAT IS IT GOOD FOR?
integrated Tahoe-LAFS with existing systems, including
Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django,
Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and
-more. See the Related Projects page on the wiki [5].
+more. See the Related Projects page on the wiki [3].
We believe that strong cryptography, Free and Open Source
Software, erasure coding, and principled engineering practices
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 fifteenth release in the version 1 series. This
+This is the seventeenth 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
ACKNOWLEDGEMENTS
-This is the ninth release of Tahoe-LAFS to be created solely
+This is the eleventh 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
+David-Sarah Hopwood
on behalf of the Tahoe-LAFS team
-October 31, 2011
-San Francisco, California, USA
+July 3, 2012
+Rainhill, Merseyside, UK
-[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/NEWS.rst?rev=5356
+[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
[4] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.GPL
[5] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.TGPPL.rst
-[6] https://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.rst
+[6] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst
[7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
[8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap
-[9] https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/CREDITS?rev=5356
+[9] https://tahoe-lafs.org/trac/tahoe-lafs/browser/CREDITS
[10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev
[11] http://atlasnetworks.us/
-[12] http://leastauthority.com/
+[12] https://leastauthority.com/
[13] https://tahoe-lafs.org/hacktahoelafs/