Leaderboard

Dear contributors, We plan to perform a long-discussed migration to git as our version control system. We have been very happy with SVN for a long time, for its simplicity and its ability to handle our game assets. But we yearn for the collaborative features of git and for the many git-based tools that would allow for a more efficient development process. We managed to keep using SVN and to collaborate efficiently on Phabricator for the past 6 years, but unfortunately all good things must come to an end, and Phabricator is now unmaintained. We thus decided to take the plunge and to migrate to git, and we have chosen Gitea as our self-hosted git forge. Our historical Trac bug-tracker will become read-only, and its contents (tickets, wiki) will be entirely migrated to our Gitea instance. After some time, Trac will be stopped, and links to Trac will be redirected to Gitea. Access to our Phabricator instance will be restricted so that our contributors can port their open work to Gitea. After some time, all sensitive user data will be deleted from Phabricator, which will become read-only. Please keep in mind that, even though Phabricator holds a meaningful history of important discussions, it constitutes a security liability. We cannot guarantee to keep it online indefinitely. No ready-made tool exists, at this moment, to migrate Phabricator discussions to Gitea. The migration is planned to happen on the 19th and 20th of August (European hours). During these two days, the aforementioned services (Trac, Phabricator) and the SVN repositories will be down. Development progress will be halted. We plan to provide a functional git-based development environment immediately after the migration. Most CI/CD systems are ready to be launched, and user documentation is ready. But the transition to a new development flow will, of course, take some time. We hope that this transition will allow us to make swift progress on the long-awaited release of the next Alpha.

Here is a changelog of my work since last time: numerous infrastructure tweaks for the new server SPIR-V shaders are generated in the nightly build and can be downloaded in a git clone - this removes the need for a spirv mod entirely added git hooks to prevent upload of binary files in case a user hasn't installed git-lfs; to enforce a linear commit history by default; added size limits to git uploads finished all the CI pipelines for Linux, Windows, and macOS finished the workflow refactoring for macOS updated the wiki page for the CI/CD setup fixed references to dropped commits in the history addressed some remarks above as commented, looked into the translation alternative disabled localization of Gitea, since English is supposed to be used for collaboration, and the contents of Gitea (main page, wiki, policies, ..) are not localizable anyway I tested everything I planned to test on the server we will use, so I am ready to perform the migration on the 19th and 20th of August. I have a few nice improvements I will implement in the next couple days (issue templates, code owners, and more). I made sure that sha256 repos are available in Gitea after the migration (they are not available on my PoC due to an older git version). Unfortunately, reposurgeon, which is used to convert the SVN repo into a git repo, does not seem to support SHA-256. Reading the documentation, it looks like the tool internally relies a lot on SHA-1 to work. So I cannot generate a SHA-256 repo. git-filter-repo, with which I rewrite history afterwards, does not propose conversion from SHA-1 to SHA-256 either.

I'd suggest really looking into DE's groves. They'd solve this, as most forests would be made of undeletable Groves.

Okay, tried it. I'm wondering why we just don't do it for all buildings (delete straggler trees) and add DE's Groves (which aren't deletable).

When I play Britons and my allies play Gauls and Mauryas