One of the philosophies in the construction of relax is that if there is something which is not immediately obvious then that is considered a design bug. If any flaws in relax are uncovered including general design flaws, bugs in the code, or documentation issues these can be reported within relax's bug tracker system. Please submit a relax bug here rather than reporting bugs to personal email addresses or to the mailing lists.
When reporting a bug please include as much information as possible so that the problem can be reproduced. Include information such as the release version or the revision number if the repository sources are being used. Also include all the steps performed in order to trigger the bug. Attachment of files is allowed so scripts and subsets of the input data can be included. However please do not attach large files to the report. Prior to reporting the bug try to make sure that the problem is indeed a bug and if you have any doubts please feel free to ask on the relax-users mailing list. To avoid duplicates be sure that the bug has not already been submitted to the bug tracker. You can search through the bugs here.
Once the bug has been confirmed by one of the relax developers you may speed up the resolution of the problem by trying to fixing the bug yourself. If you do wish to play with the source code and try to fix the issue see the relax development chapter of this manual on how to check out the latest sources (Chapter 13 on page ), how to generate a patch (which is just the output of diff in the `unified' format), and the guidelines for the format of the code.
The relax user manual (PDF), created 2019-03-08.