source: trunk/relnotes.txt

Last change on this file was 8f983cb, checked in by meejah <meejah@…>, at 2020-03-11T23:38:03Z

bump version to 1.14.0 and update release notes

  • Property mode set to 100644
File size: 6.4 KB
Line 
1ANNOUNCING Tahoe, the Least-Authority File Store, v1.14.0
2
3The Tahoe-LAFS team is pleased to announce version 1.14.0 of
4Tahoe-LAFS, an extremely reliable decentralized storage
5system. Get it with "pip install tahoe-lafs", or download a
6tarball here:
7
8  https://tahoe-lafs.org/downloads
9
10Tahoe-LAFS is the first distributed storage system to offer
11"provider-independent security" — meaning that not even the
12operators of your storage servers can read or alter your data
13without your consent. Here is the one-page explanation of its
14unique security and fault-tolerance properties:
15
16  https://tahoe-lafs.readthedocs.org/en/latest/about.html
17
18The previous stable release of Tahoe-LAFS was v1.12.1,
19released on January 18, 2017.
20
21The v1.14.0 release: makes several Magic Folder improvements (MacOS
22support, better logs, fewer conflict cases); adds an Eliot streaming
23logs endpoint; adds an extension point for storage customization;
24makes a bunch of bug-fixes and cleanups. NixOS is a supported
25platform; Fedora 29 is no longer a supported platform. Several early
26parts of Python3 porting have landed.
27
28DEPRECATED: ``tahoe start``, ``tahoe stop``, ``tahoe restart`` and
29``tahoe daemonize`` are all deprecated in favour of using ``tahoe
30run`` (along with a suitable process manager if desired).
31
32Please see ``NEWS.rst`` for a more complete list of changes.
33
34
35WHAT IS IT GOOD FOR?
36
37With Tahoe-LAFS, you distribute your data across multiple
38servers. Even if some of the servers fail or are taken over
39by an attacker, the entire file store continues to function
40correctly, preserving your privacy and security. You can
41easily share specific files and directories with other people.
42
43In addition to the core storage system itself, volunteers
44have built other projects on top of Tahoe-LAFS and have
45integrated Tahoe-LAFS with existing systems, including
46Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django,
47Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and
48more. See the Related Projects page on the wiki [3].
49
50We believe that strong cryptography, Free and Open Source
51Software, erasure coding, and principled engineering practices
52make Tahoe-LAFS safer than RAID, removable drive, tape,
53on-line backup or cloud storage.
54
55This software is developed under test-driven development, and
56there are no known bugs or security flaws which would
57compromise confidentiality or data integrity under recommended
58use. (For all important issues that we are currently aware of
59please see the known_issues.rst file [2].)
60
61
62COMPATIBILITY
63
64This release should be compatible with the version 1 series of
65Tahoe-LAFS. Clients from this release can write files and
66directories in the format used by clients of all versions back
67to v1.0 (which was released March 25, 2008). Clients from this
68release can read files and directories produced by clients of
69all versions since v1.0.
70
71Network connections are limited by the Introducer protocol in
72use. If the Introducer is running v1.10 or v1.11, then servers
73from this release (v1.12) can serve clients of all versions
74back to v1.0 . If it is running v1.12, then they can only
75serve clients back to v1.10. Clients from this release can use
76servers back to v1.10, but not older servers.
77
78Except for the new optional MDMF format, we have not made any
79intentional compatibility changes. However we do not yet have
80the test infrastructure to continuously verify that all new
81versions are interoperable with previous versions. We intend
82to build such an infrastructure in the future.
83
84This is the twenty-first release in the version 1 series. This
85series of Tahoe-LAFS will be actively supported and maintained
86for the foreseeable future, and future versions of Tahoe-LAFS
87will retain the ability to read and write files compatible
88with this series.
89
90
91LICENCE
92
93You may use this package under the GNU General Public License,
94version 2 or, at your option, any later version. See the file
95"COPYING.GPL" [4] for the terms of the GNU General Public
96License, version 2.
97
98You may use this package under the Transitive Grace Period
99Public Licence, version 1 or, at your option, any later
100version. (The Transitive Grace Period Public Licence has
101requirements similar to the GPL except that it allows you to
102delay for up to twelve months after you redistribute a derived
103work before releasing the source code of your derived work.)
104See the file "COPYING.TGPPL.rst" [5] for the terms of the
105Transitive Grace Period Public Licence, version 1.
106
107(You may choose to use this package under the terms of either
108licence, at your option.)
109
110
111INSTALLATION
112
113Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD,
114and probably most other systems. Start with "docs/INSTALL.rst"
115[6].
116
117
118HACKING AND COMMUNITY
119
120Please join us on the mailing list [7]. Patches are gratefully
121accepted -- the Roadmap page [8] shows the next improvements
122that we plan to make and CREDITS [9] lists the names of people
123who've contributed to the project. The Dev page [10] contains
124resources for hackers.
125
126
127SPONSORSHIP
128
129A special thanks goes out to Least Authority Enterprises [12],
130which employs several Tahoe-LAFS developers, for their
131continued support.
132
133HACK TAHOE-LAFS!
134
135If you can find a security flaw in Tahoe-LAFS which is serious
136enough that we feel compelled to warn our users and issue a fix,
137then we will award you with a customized t-shirt with your
138exploit printed on it and add you to the "Hack Tahoe-LAFS Hall
139Of Fame" [13].
140
141
142ACKNOWLEDGEMENTS
143
144This is the eighteenth release of Tahoe-LAFS to be created
145solely as a labor of love by volunteers. Thank you very much
146to the team of "hackers in the public interest" who make
147Tahoe-LAFS possible.
148
149Brian Warner
150on behalf of the Tahoe-LAFS team
151
152May 17, 2018
153San Francisco, California, USA
154
155
156[1] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.14.0/NEWS.rst
157[2] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst
158[3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
159[4] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.14.0/COPYING.GPL
160[5] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.14.0/COPYING.TGPPL.rst
161[6] https://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.14.0/INSTALL.html
162[7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
163[8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap
164[9] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/CREDITS
165[10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev
166[12] https://leastauthority.com/
167[13] https://tahoe-lafs.org/hacktahoelafs/
168[14] https://github.com/warner/magic-wormhole
Note: See TracBrowser for help on using the repository browser.