[tahoe-dev] [tahoe-lafs] #652: "appname" in version shouldn't change keys of "tahoe --version"

[tahoe-lafs]

#652: "appname" in version shouldn't change keys of "tahoe --version"
-------------------------------------------+--------------------------------
 Reporter:  warner                         |           Owner:  somebody
     Type:  defect                         |          Status:  new     
 Priority:  major                          |       Milestone:  1.7.0   
Component:  packaging                      |         Version:  1.3.0   
 Keywords:  version forward-compatibility  |   Launchpad_bug:          
-------------------------------------------+--------------------------------

Comment(by zooko):

 Let's see where are the docs of our versioning scheme...

 Here:

 http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Versioning

 So the current protocol version is "v1" and I guess it will remain "v1"
 until we switch to an entirely new protocol layered on top of HTTP instead
 of on top of TCP+SSL+Foolscap (#510). The current storage servers return a
 version dict like this to describe themselves:

 {{{
 { "http://allmydata.org/tahoe/protocols/storage/v1" :
                             { "maximum-immutable-share-size":
 remaining_space,
                               "tolerates-immutable-read-overrun": True,
                               "delete-mutable-shares-with-zero-length-
 writev": True,
                               },
                             "application-version": "allmydata-
 tahoe/1.6.1-r4264",
                             }
 }}}

 (See [source:src/allmydata/storage/server.py at 4164#L267].)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/652#comment:5>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid