https://github.com/ArmagetronAd
There and on gitlab, in the armagetronad module, I added a bunch of new branches: (lp: not followed by ~ is short for lp:~/armagetronad-dev/armagetronad/) Branch names in bold.
feature-fortress-ai mirrors lp:0.4-armagetronad-fortress_ai which is derived from lp:trunk-armagetronad-fortress_ai. That's the experimental fortress AI. I mostly abandoned it because at one point, merging from the mainline became a nightmare. Now that the branch is converted, I discovered the reason (short version: bzr doesn't handle criss-cross merges very well) and corrected it.
feature-cmake mirrors lp:0.4-armagetronad-cmake which is derived from lp:trunk-cmake. That was a whole other nightmare. trunk-cmake is stacked on trunk-armagetronad-work, but both branches are in different formats. Because both are broken, neither can be upgraded, and fetching a copy failed. Combining them into one non-stacked branch on the lp servers would be possible, for example if lp merge requests could be executed on the servers... but they can't. Luckily, I found a local copy between the sofa cushions.
Let's say my opinion of lp in particular and bzr in general has not improved in the past week. While it was probably bzr-svn that caused the corruption, lp should not have allowed broken branches to be uploaded.
The hack-0.2.8- branches are synced from the relevant famous ap/ct/sty branches. I only tested the plain sty one, it seems to be possible to merge from master with a non-overwhelming amount of conflicts. sty+ct+ap gets 109 by gits count. Could be worse!
kyle gave be some bzr branches to move over from being related to trunk-armagetronad-work or 0.4-armagetronad-work to the new 0.4-armagetronad, namely
lp:~armagetronad-sty-0.3/armagetronad/armagetronad-v2sty
lp:~armagetronad-ct/armagetronad/armagetronad-ct
lp:~armagetronad-ct/armagetronad/armagetronad-ct-ladderlog
The transformed git branches are lp:~z-man/armagetronad/0.4-(old branch name)-unified, the git branches are hack-(old branch name without armagetronad-).
lp:~armagetronad-ct/armagetronad/0.4-delaycmd has become feature-delaycmd.
Looks like a single feature? Should I transform that to a pull request and merge into master directly? I'm just going by the title and the small history at the moment

Yeah, that's a lot of branches. We should probably merge them or abandon them soonish.
I'm currently the only one with write access on github and gitlab. Two reasons for that: I don't know any of your logins there, and I'd like to try the model where only half a handful of maintainers have direct write access and regular and irregular devs alike submit pull/merge requests (to master, not legacy_0.2.8, obv) from their private copies of the repositories. The maintainers' own work would go the same route (already practiced), and ideally, they'd check each other's work. Thoughts? Pull/Merge requests? Maintainer volunteers? No need to hurry, at the current pace, I can do the job alone
