Difference between revisions of "Beta Testing"
From GhostBSD Wiki
m (4 revisions imported) |
m |
||
| Line 3: | Line 3: | ||
If you have a spare 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. | If you have a spare 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. | ||
| − | If | + | If you want to become a tester, let us know by contacting us at one of the following locations: |
| + | * Telegram at https://t.me/ghostbsd | ||
| + | * The IRC channels are <code>#ghostbsd</code> and <code>#ghostbsd-dev</code> on irc://irc.freenode.net. | ||
| + | * You can access the IRC channel [http://ghostbsd.org/irc/ via our web user interface]. | ||
| + | * The forums are available at http://forums.ghostbsd.org/ | ||
| + | ==Download the latest development media== | ||
| + | The latest GhostBSD development installation media can be found [https://download.ghostbsd.com/releases/amd64/ISO-IMAGES/latest here]. | ||
| + | |||
| + | ==Reporting issues== | ||
Anyone can become a beta tester. Follow these tips so that you can accurately describe your findings so they can be fixed as soon as possible: | Anyone can become a beta tester. Follow these tips so that you can accurately describe your findings so they can be fixed as soon as possible: | ||
| − | * before reporting a bug, search the [ | + | * 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. | * 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. | ||
Revision as of 00:33, 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 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.
If you want to become a tester, let us know by contacting us at one of the following 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 media
The latest GhostBSD development installation media can be found here.
Reporting issues
Anyone can become a beta tester. Follow these tips so that you can accurately describe your findings so they can be fixed as soon as possible:
- 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 other info that may be useful.
- if the problem appears to be hardware related, include a copy of /var/run/dmesg.boot as this file shows the hardware that was probed the last time the GhostBSD system booted.
