mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-01-18 02:40:07 +00:00
Release notes, NEWS, and quickstart updates for 1.9.2a1. refs #1776
This commit is contained in:
parent
33e2d2962e
commit
8c256de1f0
51
NEWS.rst
51
NEWS.rst
@ -3,6 +3,57 @@
|
|||||||
User-Visible Changes in Tahoe-LAFS
|
User-Visible Changes in Tahoe-LAFS
|
||||||
==================================
|
==================================
|
||||||
|
|
||||||
|
Release 1.9.2a1 (2012-06-23)
|
||||||
|
----------------------------
|
||||||
|
|
||||||
|
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.
|
||||||
|
- FTP can now list directories containing mutable files, although it
|
||||||
|
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`)
|
||||||
|
- 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`)
|
||||||
|
|
||||||
|
Configuration/Behaviour 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`)
|
||||||
|
|
||||||
|
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`)
|
||||||
|
|
||||||
|
.. _`#680`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/680
|
||||||
|
.. _`#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
|
||||||
|
.. _`#1628`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1628
|
||||||
|
.. _`#1631`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1631
|
||||||
|
.. _`#1636`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1636
|
||||||
|
.. _`#1655`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1655
|
||||||
|
.. _`#1669`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1669
|
||||||
|
.. _`#1670`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1670
|
||||||
|
.. _`#1676`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1676
|
||||||
|
.. _`#1688`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1688
|
||||||
|
.. _`#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
|
||||||
|
|
||||||
|
|
||||||
Release 1.9.1 (2012-01-12)
|
Release 1.9.1 (2012-01-12)
|
||||||
--------------------------
|
--------------------------
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ want to read `the "historical known issues" document`_.
|
|||||||
.. _the "historical known issues" document: historical/historical_known_issues.txt
|
.. _the "historical known issues" document: historical/historical_known_issues.txt
|
||||||
|
|
||||||
|
|
||||||
Known Issues in Tahoe-LAFS v1.9.1, released 12-Jan-2012
|
Known Issues in Tahoe-LAFS v1.9.2, released 23-Jun-2012
|
||||||
=======================================================
|
=======================================================
|
||||||
|
|
||||||
* `Unauthorized access by JavaScript in unrelated files`_
|
* `Unauthorized access by JavaScript in unrelated files`_
|
||||||
|
24
relnotes.txt
24
relnotes.txt
@ -1,7 +1,7 @@
|
|||||||
ANNOUNCING Tahoe, the Least-Authority File System, v1.9.1
|
ANNOUNCING Tahoe, the Least-Authority File System, v1.9.2a1
|
||||||
|
|
||||||
The Tahoe-LAFS team is pleased to announce the immediate
|
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.9.2a1 of Tahoe-LAFS, an extremely
|
||||||
reliable distributed storage system. Get it here:
|
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/quickstart.rst
|
||||||
@ -14,12 +14,11 @@ unique security and fault-tolerance properties:
|
|||||||
|
|
||||||
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
|
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
|
||||||
|
|
||||||
The previous stable release of Tahoe-LAFS was v1.9.0, released
|
The previous stable release of Tahoe-LAFS was v1.9.1, released
|
||||||
on October 31, 2011.
|
on January 12, 2012.
|
||||||
|
|
||||||
v1.9.1 is a critical bugfix release which fixes a significant
|
v1.9.2 will be a bugfix release that primarily fixes regressions
|
||||||
security issue [#1654]. See the NEWS file [1] and known_issues.rst
|
in mutable file support. See the NEWS file [1] for details.
|
||||||
[2] file for details.
|
|
||||||
|
|
||||||
|
|
||||||
WHAT IS IT GOOD FOR?
|
WHAT IS IT GOOD FOR?
|
||||||
@ -61,7 +60,7 @@ all versions since v1.0. Servers from this release can serve
|
|||||||
clients of all versions back to v1.0 and clients from this
|
clients of all versions back to v1.0 and clients from this
|
||||||
release can use servers of all versions back to v1.0.
|
release can use servers of all versions back to v1.0.
|
||||||
|
|
||||||
This is the sixteenth 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
|
series of Tahoe-LAFS will be actively supported and maintained
|
||||||
for the foreseeable future, and future versions of Tahoe-LAFS
|
for the foreseeable future, and future versions of Tahoe-LAFS
|
||||||
will retain the ability to read and write files compatible
|
will retain the ability to read and write files compatible
|
||||||
@ -125,19 +124,18 @@ Of Fame" [13].
|
|||||||
|
|
||||||
ACKNOWLEDGEMENTS
|
ACKNOWLEDGEMENTS
|
||||||
|
|
||||||
This is the tenth 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
|
as a labor of love by volunteers. Thank you very much to the
|
||||||
team of "hackers in the public interest" who make Tahoe-LAFS
|
team of "hackers in the public interest" who make Tahoe-LAFS
|
||||||
possible.
|
possible.
|
||||||
|
|
||||||
Brian Warner
|
David-Sarah Hopwood
|
||||||
on behalf of the Tahoe-LAFS team
|
on behalf of the Tahoe-LAFS team
|
||||||
|
|
||||||
January 12, 2011
|
June 23, 2012
|
||||||
San Francisco, California, USA
|
Rainhill, Merseyside, UK
|
||||||
|
|
||||||
|
|
||||||
[#1654] https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
|
|
||||||
[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst
|
[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst
|
||||||
[2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst
|
[2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst
|
||||||
[3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
|
[3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
|
||||||
|
Loading…
Reference in New Issue
Block a user