Brian Masinick
By the way, the release we are discussing here is a RELEASE CANDIDATE – the first one.
If you have any defects that you would like to see resolved, it sure would be an excellent time to do so BEFORE this release candidate becomes THE release antiX 26.
If you do find things you believe are incorrect, please do the following:
1) Share your information report; typically a FULL information report is best; inxi -Fxz is one possible way to do this; inxi -zv8 provides just about every piece of information possible, but it’s a really BIG report; choose which one shows the hardware you’re most interested in based on your problem report. Usually you can include these in an attachment; if yes, put it into a file with a filename ending in .txt.
2) Describe the problem, first in a brief abstract, usually you should create a new topic for your issue; the abstract could be the title of the post.
3) Next describe the issue in detail, and explain, step by step, how you encountered the problem. Then explain what you expected the result to be, and finally what the actual results were.
4) If possible, share one or two screen attachments (if more than one, you may need a reply message for each extra image.
5) Share as much as you believe is necessary, but be sure to provide enough details so the developer and tester can actually either replicate the problem or at least determine the likely reason in order to analyze the relevant code or configuration and figure out a solution.
It’s probably best NOT to put the full report here, but you CAN provide a link in this topic to your incident report topic.
I hope we don’t have too many outstanding issues, but even if we do, it’s better to identify them as soon as possible and resolve them, and I thank you all for the considerable cooperation we have received throughout this development effort!
--
Brian Masinick
Alternate "Search B":
This search page