[tahoe-lafs-trac-stream] [tahoe-lafs] #1482: change the hostname in the version strings from allmydata.org

[tahoe-lafs]

#1482: change the hostname in the version strings from allmydata.org
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  somebody
         Type:  defect   |     Status:  new
     Priority:  minor    |  Milestone:  undecided
    Component:  code     |    Version:  1.8.2
   Resolution:           |   Keywords:  versioning forward-compatibility
Launchpad Bug:           |  backward-compatibility
-------------------------+-------------------------------------------------
Description changed by zooko:

Old description:

> Our protocol versioning scheme uses URLs to indicate specific versions of
> things. Those URLs currently have hostname "allmydata.org" but we've
> moved to make "tahoe-lafs.org" our primary hostname for the open source
> project. Should we change those URLs? Would that confuse clients that are
> using those URLs for version indicators -- would they think that this
> means a new (and presumably incompatible) version of the protocols in
> question and thus refuse to interoperate or something?

New description:

 Our protocol versioning scheme uses URLs to indicate specific versions of
 things. Those URLs currently have hostname "allmydata.org" but we've moved
 to make "tahoe-lafs.org" our primary hostname for the open source project.
 Should we change those URLs? Would that confuse clients that are using
 those URLs for version indicators -- would they think that this means a
 new (and presumably incompatible) version of the protocols in question and
 thus refuse to interoperate or something?

 [wiki:Versioning],
 [source:trunk/src/allmydata/introducer/server.py?annotate=blame&rev=5110
 introducer server's implementation]

--

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1482#comment:1>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage