@darius @michcia @gogobonobo I think the distinction is between was strictly correct, semver-wise, and what's pragmatic. the software _is_ hometown, so the hometown version should be the main component and the masto version is secondary. but almost everything that wants to know the version is expecting it to be a mastodon instance and so wants the mastodon version (and having it first would mean anything naively looking at the beginning of the string would get the information it expects)
Jake
@shadowfacts @michcia @darius Given that other forks are doing things even more differently, is this a "the horse has already left the barn so why close the barn doors" kind of situation?
If a client wants to be branch-compatible, I guess they have to be better about parsing the version string. But it means that the branches may not work with some plugins/clients, even though they could.
Darius - I appreciate that you thought about the convention here!