From: david-sarah Date: Sun, 28 Nov 2010 20:47:38 +0000 (-0800) Subject: Release v1.8.1. refs #1242 X-Git-Tag: allmydata-tahoe-1.8.1~3 X-Git-Url: https://git.rkrishnan.org/frontends/cyclelanguage?a=commitdiff_plain;h=841dc761870df1a8534437a0353726dd59782a18;p=tahoe-lafs%2Ftahoe-lafs.git Release v1.8.1. refs #1242 --- diff --git a/NEWS b/NEWS index 53af93d9..c94ec755 100644 --- a/NEWS +++ b/NEWS @@ -27,9 +27,21 @@ fails to unlink the file from its old location. (#1255) - 'tahoe start' now gives a more positive indication that the node has started. (#71) + - The arguments seen by 'ps' or other tools for node processes should + be more useful (in particular, they should include the path of the + 'tahoe' script, rather than an obscure tool named 'twistd'). (#174) + +** Removed Features + + - The tahoe start/stop/restart and node creation commands no longer + accept the -m or --multiple option, for consistency between platforms. + (#1262) ** Packaging + - We now host binary packages so that users on certain operating systems + can install without having a compiler. + - Use a newer version of a dependency if needed, even if an older version is installed. This would previously cause a VersionConflict error. (#1190) @@ -46,6 +58,7 @@ Tahoe-LAFS, or add anything to facilitate government access to data. (#1216) + * Release 1.8.0 (2010-09-23) ** New Features @@ -85,6 +98,7 @@ - on x86 and x86-64 platforms, pycryptopp >= 0.5.20 - pycrypto 2.2 is excluded due to a bug + * Release 1.7.1 (2010-07-18) ** Bugfixes and Improvements @@ -114,6 +128,7 @@ - Simplify and tidy-up directories, unicode support, test code (#923, #967, #1072) + * Release 1.7.0 (2010-06-18) ** New Features @@ -199,6 +214,7 @@ pycrypto >= 2.0.1 pyasn1 >= 0.0.8a mock (only required by unit tests) + * Release 1.6.1 (2010-02-27) ** Bugfixes @@ -219,6 +235,7 @@ you can view the results of an operation up to 4 days after it has completed. After viewing them for the first time, the results are retained for a further day. (#577) + * Release 1.6.0 (2010-02-01) ** New Features diff --git a/docs/how_to_make_a_tahoe-lafs_release.rst b/docs/how_to_make_a_tahoe-lafs_release.rst index aec7a99c..a9a3235c 100644 --- a/docs/how_to_make_a_tahoe-lafs_release.rst +++ b/docs/how_to_make_a_tahoe-lafs_release.rst @@ -1,19 +1,37 @@ -[ ] 1 update doc files: relnotes.txt, CREDITS, docs/known_issues.txt, NEWS. Add release name and date to top-most item in NEWS. +[ ] 1 update doc files: relnotes.txt, CREDITS, docs/known_issues.rst, NEWS. Add release name and date to top-most item in NEWS. + [ ] 2 change docs/quickstart.html to point to just the current allmydata-tahoe-X.Y.Z.zip source code file, or else to point to a directory which contains only allmydata-tahoe-X.Y.Z.* source code files + [ ] 3 darcs pull + [ ] 4 make tag + [ ] 5 build locally to make sure the release is reporting itself as the intended version + [ ] 6 make sure buildbot is green + [ ] 7 make sure other people aren't committing at that moment + [ ] 8 push tag along with some other documentation-only patch (typically to relnotes.txt) to trigger buildslaves + [ ] 9 make sure buildbot is green + [ ] 10 make sure debs got built and uploaded properly + [ ] 11 make sure a sumo sdist tarball got built and uploaded properly + [ ] 12 symlink the release tarball on tahoe-lafs.org: /var/www/source/tahoe-lafs/releases/ + [ ] 13 update Wiki: front page news, news, old news, parade of release notes + [ ] 14 send out relnotes.txt: [ ] tahoe-announce@tahoe-lafs.org, [ ] tahoe-dev@tahoe-lafs.org, [ ] p2p-hackers@lists.zooko.com, [ ] lwn@lwn.net, [ ] cap-talk@mail.eros-os.org, [ ] cryptography@metzdown.com, [ ] cryptography@randombit.net, [ ] twisted-python@twistedmatrix.com, [ ] owncloud@kde.org, [ ] liberationtech@lists.stanford.edu, [ ] the "decentralization" group on groups.yahoo.com, [ ] pycrypto mailing list, -> fuse-devel@lists.sourceforge.net, -> fuse-sshfs@lists.sourceforge.net, [ ] duplicity-talk@nongnu.org, [ ] news@phoronix.com, [ ] python-list@python.org, -> cygwin@cygwin.com, [ ] The Boulder Linux Users' Group, [ ] The Boulder Hackerspace mailing list, [ ] cryptopp-users@googlegroups.com, [ ] tiddlywiki, [ ] hdfs-dev@hadoop.apache.org, [ ] bzr, [ ] mercurial, [ ] http://listcultures.org/pipermail/p2presearch_listcultures.org/ , deltacloud, libcloud, [ ] swift@lists.launchpad.net, cleversafe.org, [ ] stephen@fosketts.net, [ ] Chris Mellor of The Register, [ ] nosql@mypopescu.com + [ ] 15 update hacktahoe.org + [ ] 16 make an "announcement of new release" on freshmeat + [ ] 17 upload to pypi with "python ./setup.py sdist upload register" + [ ] 18 make an "announcement of new release" on launchpad + [ ] 19 close the Milestone on the trac Roadmap diff --git a/docs/known_issues.rst b/docs/known_issues.rst index 515624f3..521a4306 100644 --- a/docs/known_issues.rst +++ b/docs/known_issues.rst @@ -3,7 +3,7 @@ Known issues ============ * `Overview`_ -* `Issues in Tahoe-LAFS v1.8.0, released 2010-09-23` +* `Issues in Tahoe-LAFS v1.8.1, released 2010-11-28` * `Potential unauthorized access by JavaScript in unrelated files`_ * `Potential disclosure of file through embedded hyperlinks or JavaScript in that file`_ @@ -25,7 +25,7 @@ want to read the "historical known issues" document: http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/historical/historical_known_issues.txt -Issues in Tahoe-LAFS v1.8.0, released 2010-09-23 +Issues in Tahoe-LAFS v1.8.1, released 2010-11-28 ================================================ Potential unauthorized access by JavaScript in unrelated files diff --git a/docs/quickstart.html b/docs/quickstart.html index e6e9eb43..d048a3d2 100644 --- a/docs/quickstart.html +++ b/docs/quickstart.html @@ -27,15 +27,15 @@

Get Tahoe-LAFS

-

Download the latest stable release, v1.8.0:

+

Download the latest stable release, v1.8.1:

http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.8.0.zip
+ href="http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.8.0.zip">http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.8.1.zip

Set Up Tahoe-LAFS

Unpack the zip file and cd into the top-level directory.

-

Run python setup.py build to generate the tahoe executable in a subdirectory of the current directory named bin.

+

Run python setup.py build to generate the tahoe executable in a subdirectory of the current directory named bin. This will download and build anything you need from various websites.

On Windows, the build step might tell you to open a new Command Prompt (or, on XP and earlier, to log out and back in again). This is needed the first time you set up Tahoe-LAFS on a particular installation of Windows.

diff --git a/relnotes.txt b/relnotes.txt index b2f586d4..9e109dbf 100644 --- a/relnotes.txt +++ b/relnotes.txt @@ -1,7 +1,7 @@ -ANNOUNCING Tahoe, the Least-Authority File System, v1.8.0 +ANNOUNCING Tahoe, the Least-Authority File System, v1.8.1 The Tahoe-LAFS team is pleased to announce the immediate -availability of version 1.8.0 of Tahoe-LAFS, an extremely +availability of version 1.8.1 of Tahoe-LAFS, an extremely reliable distributed storage system. Get it here: http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.html @@ -14,12 +14,13 @@ unique security and fault-tolerance properties: http://tahoe-lafs.org/source/tahoe/trunk/docs/about.html -The previous stable release of Tahoe-LAFS was v1.7.1, which was -released July 18, 2010 [1]. +The previous stable release of Tahoe-LAFS was v1.8.0, which was +released September 23, 2010 [1]. -v1.8.0 offers greatly improved performance and fault-tolerance -of downloads and improved Windows support. See the NEWS file -[2] for details. +v1.8.1 is a stable bugfix release correcting a number of minor +issues. It also includes a modest performance improvement in +downloading, and a fix for a security issue involving HTTP +proxies. See the NEWS file [2] for details. WHAT IS IT GOOD FOR? @@ -140,12 +141,12 @@ possible. David-Sarah Hopwood and Zooko Wilcox-O'Hearn on behalf of the Tahoe-LAFS team -September 23, 2010 +November 28, 2010 Rainhill, Merseyside, UK and Boulder, Colorado, USA -[1] http://tahoe-lafs.org/trac/tahoe/browser/relnotes.txt?rev=4579 -[2] http://tahoe-lafs.org/trac/tahoe/browser/NEWS?rev=4732 +[1] http://tahoe-lafs.org/trac/tahoe/browser/relnotes.txt?rev=4747 +[2] http://tahoe-lafs.org/trac/tahoe/browser/NEWS?rev=4854 [3] http://tahoe-lafs.org/trac/tahoe/wiki/RelatedProjects [4] http://tahoe-lafs.org/trac/tahoe/browser/docs/known_issues.txt [5] http://tahoe-lafs.org/trac/tahoe/browser/COPYING.GPL @@ -153,6 +154,6 @@ Rainhill, Merseyside, UK and Boulder, Colorado, USA [7] http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.html [8] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev [9] http://tahoe-lafs.org/trac/tahoe/roadmap -[10] http://tahoe-lafs.org/trac/tahoe/browser/CREDITS?rev=4591 +[10] http://tahoe-lafs.org/trac/tahoe/browser/CREDITS?rev=4797 [11] http://tahoe-lafs.org/trac/tahoe/wiki/Dev [12] http://tahoe-lafs.org/hacktahoelafs/