[tahoe-lafs-trac-stream] [tahoe-lafs] #1773: check/test/update claim about compatibility with old clients and servers in relnotes.txt
tahoe-lafs
trac at tahoe-lafs.org
Fri Mar 15 07:48:47 UTC 2013
#1773: check/test/update claim about compatibility with old clients and servers in
relnotes.txt
-------------------------+-------------------------------------------------
Reporter: | Owner: marlowe
davidsarah | Status: new
Type: defect | Milestone: 1.10.0
Priority: normal | Version: 1.9.1
Component: | Keywords: relnotes docs backward-
documentation | compatibility
Resolution: |
Launchpad Bug: |
-------------------------+-------------------------------------------------
Comment (by ClashTheBunny):
We don't anymore. It used to be done. Here's zooko's statement on this:
> > It would be cool for someone to set up to run inter-node regression
tests of various versions.
>
> Yes, that would! I value backward-compatibility, because I recognize
> that people are often more conservative about storage than about other
> kinds of software.
>
> There used to be a thing called Memory Lane:
>
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid?version=54
>
> But it needs a maintainer:
>
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1002# do some
> renovations on Memory Lane
>
> That would be a pretty cool thing to have on the live Test Grid, so if
> you had a question like "What happens if you upload a new
> XSalsa20-encrypted file using Tahoe-LAFS v14.1 to a grid with one
> Tahoe-LAFS storage server of each version going back a few years:
> 1.10.0, 1.9.2, 1.8.3, 1.7.1, 1.6.1, 1.5, 1.4.1, 1.3, 1.2, 1.1, and
> 1.0, what happens?", then you can just try it and see! (Hopefully the
> answer is It Just Works because the storage servers don't know what
> kind of encryption you are using on the client side. ☺)
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1773#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list