FreeOrion

> And I see your name in these branches. Are you talking with yourself?

If you have nothing of value to contribute then shut the fuck up.

On the freeorion there are several branches, which are more than 6 month old and are not release branches. Those branches clutter my local autocompletion for no good reason. This includes: InvadeThroughShields Noisiness PreWarpStart TechTurnsReductionNotCost adrianbroher/breathe-docs adrianbroher/ci...

> Meanwhile I'm going to postpone the creation of the release branch as suggested, until this is sorted out.

Why? The reporter made clear that he doesn't want to stick to the report process. I don't see a reason why the release should be put on hold down because of someones special needs.

Seems like the class dependencies are all over the place (no different than the C++ code to be honest).

> I post this graph just to track AI progress through the years.

So this is the initial state for now?

Does this graph also include the unit test code?

Oberlus wrote: ↑Sun Apr 26, 2020 6:43 pm It is ThinkSome who complains about this from time to time in chatroom

Ah, so he's that specing guy?

Oberlus wrote: ↑Sun Apr 26, 2020 6:43 pm … but won't open an issue for it because he has a problem with GitHub.

Tough luck, then the issue will be forgotton for certain.

The blog article is incomplete:

https://github.com/git/git/security/adv ... -c969-7j4q

> So, thanks a lot for your work and a great game so far! I'll lurk around more and see if/how I can contribute (no programmer, sorry). That entirely depends on how much time you are willing to contribute and what your skills are. I usually consider the following tasks good entry level tasks for eve...

Github released own CI. It is free for opensource. Can replace both Travis and Appveyor. https://github.com/features/actions Workflows run in Linux, macOS, Windows, and containers on GitHub-hosted machines, called 'runners'. Alternatively, you can also host your own runners to run workflows on mach...

It would be nice if you could post notes related to st-tool into the Github Issue tracker in the future.

Oberlus wrote: ↑Sun Apr 12, 2020 11:46 am

adrian_broher wrote: ↑Sun Apr 12, 2020 11:24 amThere is a setting for that:

The meld I installed from ubuntu repo doesn't have a preferences window. I'll search for a better version.

https://askubuntu.com/questions/1093428 ... ces-option

To see where I am, I first do freeorion$ ./check/st-tool.py compare default/stringtables/en.txt default/stringtables/es.txt default/stringtables/es.txt:24: Value of key 'OK' is identical to reference file default/stringtables/en.txt:24 [...] default/stringtables/es.txt:203: Key 'NEW_ASTEROIDS_SUFFI...

And I'm working in meld, which is quite annoying due to lack of line wrapping, but I like to see the English original values and sometimes it is helpful to be able to copy the English values for translation. There is a setting for that: https://www.howtoforge.com/images/beginners-guide-to-visual-me...

But I think I've read somewhere that "untranslated" keys should not be included. Sometimes I acknowledge that refers to entries pending of translation, but I am unsure about entries that do not require translation. If I use my brains, I think the right answer is to include such entries in...

Did you build from a new build tree?

Why did you pass the header and library locations manually?

I would change all those descriptions for others more tightly related to their real capabilities/characteristics: type (level) of weaponry, armor and shields. I would say this deserves an issue in github? But not a pressing matter, indeed. I suggest you create an issue anyway, note the problematic ...