If you already know the program, you may want to skip to the List of Test Drivers. If you are unsure whether to add something or make a change to this page, just talk about it.

Due to the sheer amount of hardware architectures, operating systems, distributions, compilers, libraries, graphics cards, X11 clients, and everything else out there, it is nearly impossible to test all these combinations with a finite number of developers. But on the other hand, we can distribute the testing effort among each of us in addition to the developer tests.

So the idea was born that every test driver tests their specific and beloved setup on the hardware they already own and everything else at their fingertips. Preferably during normal use to keep the effort involved to a minimum. Overall, these individual and highly specific tests can thus deliver comprehensive results and a broad coverage, closing the gaps and squashing even hidden bugs.

As soon as a new feature has been developed or a new version of XLibre is due, the test drivers will be kindly asked in the corresponding issues whether they can test them on their machine. When handing over the issue, specific steps are described as to what needs to be done. The selection of the involved test drivers will be made taking into account the respective requirements in accordance with the information in the table below.

To provide the software under test, we are looking into creating easily usable beta package repositories. In the cases where this is not feasible, we will provide detailed build instructions. In the future, we also want to develop dedicated test cases and request them specifically with the option to automatically run them locally.

Of course, this is all voluntary, and each test driver can decide on a case-by-case basis whether they want to participate.

To become a test driver, please add your Github handle, short description of hardware and distribution to the list. If you have some special use case like a not so common C library, non GCC compiler, utilization of specific hardware features, APIs or platforms like Nvidia CUDA etc., then please add this information to your row too. Thank you very much. Now get your helmet ready and check your seatbelt! ;-)

R - willing to test releases through package manager. (before hitting stable repository in distro) PR - have time to compile Xlibre and apply pull request if requested (mentioned) in https://github.com/X11Libre/xserver/pull/ discussions GDB - not afraid to start XLibre though gdb or using gdb -p 1234 and help provide backtraces of running session.

We all know that life's focus may shift, priorities change, and time slots become smaller in favor of other things. No problem. To leave the XLibre Test drivers program, simply remove the row with your name and other data from the table above. We would also appreciate it if you could leave a comment at the discussion of this page so that we can thank you warmly and say goodbye. Maybe until next time.