Opened at 2011-08-13T05:12:30Z

Last modified at 2011-08-26T21:30:37Z

#1482 new defect

change the hostname in the version strings from allmydata.org

Reported by: zooko Owned by: somebody
Priority: minor Milestone: undecided
Component: code Version: 1.8.2
Keywords: versioning forward-compatibility backward-compatibility cruft Cc:
Launchpad Bug:

Description (last modified by zooko)

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?

Versioning, introducer server's implementation​

Change History (4)

comment:1 Changed at 2011-08-13T05:15:48Z by zooko

  • Description modified (diff)

comment:2 Changed at 2011-08-13T05:16:10Z by zooko

  • Description modified (diff)

comment:3 in reply to: ↑ description Changed at 2011-08-13T19:36:10Z by davidsarah

Replying to zooko:

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?

When we next make an incompatible change to each protocol, yes -- but we don't make incompatible changes very often.

comment:4 Changed at 2011-08-26T21:30:37Z by davidsarah

  • Keywords cruft added
Note: See TracTickets for help on using tickets.