Difference between revisions of "Beta Testing"
From GhostBSD Wiki
m |
m |
||
| Line 1: | Line 1: | ||
If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the GhostBSD community is by reporting problems you encounter while using GhostBSD. | If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the GhostBSD community is by reporting problems you encounter while using GhostBSD. | ||
| − | If you have a spare system | + | If you have a spare computer system or virtual machine, you can also download and try out the latest alpha, beta or release candidate snapshots. These versions are still in testing and have not been officially released yet. Having as many people as possible using GhostBSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using GhostBSD better for everyone. |
| − | + | To become a tester, contact us at one of the following online locations: | |
* Telegram at https://t.me/ghostbsd | * Telegram at https://t.me/ghostbsd | ||
* The IRC channels are <code>#ghostbsd</code> and <code>#ghostbsd-dev</code> on irc://irc.freenode.net. | * The IRC channels are <code>#ghostbsd</code> and <code>#ghostbsd-dev</code> on irc://irc.freenode.net. | ||
| Line 13: | Line 13: | ||
==Reporting issues== | ==Reporting issues== | ||
| − | + | Everyone is eligible to become a beta tester. To aid us in fixing problems as quickly as possible, be sure to accurately report findings using these tips: | |
| − | * | + | * Before reporting a bug, search the [http://forums.ghostbsd.org/ forum] to see if anyone else has reported a similar problem. |
| − | * | + | * When reporting a new issue, use a descriptive subject that includes the error and the version of GhostBSD. Ideally, the subject should be short, and contains key words about the error. |
| − | * | + | * Ensure that the body of the bug report includes the GHostBSD version. |
| − | * | + | * Give a good description of how to recreate the error. If there is an error message, include its text. |
| − | * | + | * Include any additional info that may be useful. |
| − | * | + | * If the problem appears to be hardware related, include a copy of the <code>dmesg.boot</code> file located in the /var/run directory. |
Revision as of 00:52, 3 August 2018
If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the GhostBSD community is by reporting problems you encounter while using GhostBSD.
If you have a spare computer system or virtual machine, you can also download and try out the latest alpha, beta or release candidate snapshots. These versions are still in testing and have not been officially released yet. Having as many people as possible using GhostBSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using GhostBSD better for everyone.
To become a tester, contact us at one of the following online locations:
- Telegram at https://t.me/ghostbsd
- The IRC channels are
#ghostbsdand#ghostbsd-devon irc://irc.freenode.net. - You can access the IRC channel via our web user interface.
- The forums are available at http://forums.ghostbsd.org/
Download the latest development release
The latest GhostBSD development installation media can be found here.
Reporting issues
Everyone is eligible to become a beta tester. To aid us in fixing problems as quickly as possible, be sure to accurately report findings using these tips:
- Before reporting a bug, search the forum to see if anyone else has reported a similar problem.
- When reporting a new issue, use a descriptive subject that includes the error and the version of GhostBSD. Ideally, the subject should be short, and contains key words about the error.
- Ensure that the body of the bug report includes the GHostBSD version.
- Give a good description of how to recreate the error. If there is an error message, include its text.
- Include any additional info that may be useful.
- If the problem appears to be hardware related, include a copy of the
dmesg.bootfile located in the /var/run directory.
