I'm glad to say that we're code-complete for 1.10, so I've just tagged allmydata-tahoe-1.10b1 . This should contain all the code and bugfixes that will be in 1.10, but is still lacking some documentation and release-process work:
* the NEWS file needs editing * I need to write some docs on the new #466 node keys * there are probably some lingering darcs-isms in the instructions * we probably need to do some weeding on the wiki to make sure everything referenced by the tree is present and correct * need to check that the SUMO tarball is up-to-date When we get those docs fixed up, I'll tag the release candidate -rc1. Then, given a week of baking, we can release 1.10 for real, probably around the end of the month. The 1.10b1 tarballs can be downloaded from here: https://tahoe-lafs.org/source/tahoe-lafs/tarballs/allmydata-tahoe-1.10b1.zip https://tahoe-lafs.org/source/tahoe-lafs/tarballs/allmydata-tahoe-1.10b1.tar.bz2 https://tahoe-lafs.org/source/tahoe-lafs/tarballs/allmydata-tahoe-1.10b1-SUMO.zip (including all six combinations of zip/tar.gz/tar.bz and -SUMO/not-sumo). Please give beta1 a test and let us know about any problems you see, via bugs assigned to the 1.10 milestone, mail to tahoe-dev, or just mention it to a dev in IRC (#tahoe-lafs on irc.freenode.net). thanks! -Brian PS: A note for folks who run nodes from trunk: the location of the new "node key" file has moved around a bit. About four days ago (between alpha2 and beta1) I removed a fallback/workaround that tolerated an older location for this file. If you've been running a node from trunk for the last year, please look at the comments for commit e706156 and follow the instructions if they apply to you: https://github.com/tahoe-lafs/tahoe-lafs/commit/e706156323354c8e3135539a662eaf8b0314cfdc _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
