[tahoe-lafs-trac-stream] [tahoe-lafs] #1643: presence of MDMF in aliases break the CLI < v1.9.0

[tahoe-lafs]

#1643: presence of MDMF in aliases break the CLI < v1.9.0
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.9.0
  mutable                |   Keywords:  versioning forward-compatibility
   Resolution:           |  backward-compatibility mutable mdmf aliases
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 In sum:

 I'm sure that we should change trunk to have {{{forward-compatibility}}}
 as described in comment:1.

 If we're going to release a Tahoe-LAFS v1.9.1 anyway for other reasons
 [milestone:1.9.1], we might as well include this forward-compatibility
 feature in 1.9.1.

 I don't think we should go to all the effort of releasing a 1.8.4 just for
 this. People downgrading their Tahoe-LAFS back to 1.8 will hopefully be
 very rare by the time more people start manually inserting MDMF caps into
 their aliases file (especially if we fix any regressions in 1.9).

 I'm undecided about whether, when we make {{{tahoe create-alias}}} produce
 MDMF caps (at least optionally), we should have it put them into a
 separate alias file in order to avoid breaking old versions (< 1.9.1) that
 use the alias file.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1643#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage