For git, if you were using legacy_0.2.8, please switch over to legacy_0.2.9.
For bzr, the new branch name is lp:armagetronad/0.2.9 in short form or 0.2.9-armagetronad-work.
The old 0.2.8 branches still exist, but they're no longer updated. If you were in the habit of regularly merging from 0.2.8, switch to merging from 0.2.9 now. The bidirectional sync between git and bzr is still in operation, both for 0.2.8 and 0.2.9.
Equivalent operations happened on the support modules (winlibs, build_codeblocks).
Anything 0.2.8.3 stays 0.2.8.3.
On the git side, a further change was made: Our configured main branch is now named 'trunk'. Background, of course, is the increased perceived iffiness of the master-slave relationship in IT in general; my personal interpretation here is that by using these terms to describe a technical relation, one might accidentally plant the idea in people's heads that it maybe isn't such a bad model for human relations as people make it out to be. It's not about avoiding a term at all cost, that would be silly; how else are you going to talk about slavery? Also important, nobody pressured us to do this and we do not want to pressure anyone else. We, that is Tank, Lucifer, Armanelgtron, Luke-Jr (I think?) and me just had a quiet chat on IRC. Hard to believe, I know
![Smile :)](./images/smilies/icon_smile.gif)
Before you argue that point: Yes, the git main branch is traditionally called 'master' probably because the term was taken over from bitkeeper, which does have slaves, relevant links here: https://mail.gnome.org/archives/desktop ... 00066.html And the master branch is also not the master in the sense of 'master copy', the thing other equal things are copied from; the point is to have the copies only start out as copies, then modify them. And definitely it's not the master in the sense of 'very skilled person'. So it's a term that doesn't even fit in any of its regular meanings. 'trunk' is much better, see: Trees. When seen with math/computer nerd logic, anyway. I suppose botanists would protest the statement that the trunk is a branch.
The 'master' branch is still there and currently synced with trunk, but that is bound to stop some time.
Further down the line, there are going to be two more changes, no rush though:
Obviously, the Master Server also isn't really a master in any regular sense of the word. It's up for renaming. "Directory Server" is what we're hovering over. Suggestions welcome. "Hub"? It's short. But then people probably expect to be able to interact with others on the hub.
Also definitely on the chopping block: We have two instances of blacklist/whitelist in the authentication server configuration. That's just really bad for our poor Lizard Brain. They'll probably become block/allowlists.