Just an update, FWIW.
Many people have recently been drawn to computer chess in connection with the Leela chess project, which is now effectively Lc0.
Of these, most have little experience with various GUIs and engine testing. Moreover, this has become an area with even more diverse environments: in addition to many versions of Windows and Linux with .exe or app engines, now there are more .py (Python engines), cloud systems, and even phones. Distributed efforts like OpenBench (https://github.com/AndyGrant/OpenBench) also look promising. And, a good GUI for matches may not be a good choice for tuning (CLOP, etc) or online (ICS) play. There is even yet another effort to start from scratch (Octagon).
Arena is typically the first consideration, although Fritz and various other GUIs are used. Cutechess-cli seems to be the default match harness. Naturally, I still try to suggest Winboard/Xboard.
Specifically, one tester commented on the Lc0 Discord chat/blog (link from http://testserver.lczero.org/) that they tried to use time odds for a tournament with Winboard, but although the clocks adjusted as expected, once the tournament started, the starting clocks were equal. This was confusing, so they went to cutechess-cli.
Of course, I have pointed out some of the strengths of Winboard: being able to restart tournaments, and changing "concurrency" on the fly with the number of instances running (although this is somewhat less important when GPU-bound). The main weakness for me is lack of SPRT. A minor weakness is lack of random FEN/PGN starting position support (only sequential, I think), although it is easy enough to randomize the starting positions separately, which probably supports the multiple instance approach. Finally, I suspect the somewhat different Winboard and Xboard "look and feel" is due to technical historical differences (although, to be fair, I have not tried the most recent versions).
Well, enough early Sunday morning pre-coffee kick-in ramblings.
Just thought an update might be appropriate.
Huge thanks again for all of your work.
Regards,
Brian