Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
contribute:bugs:start [2018/11/17 22:59] – [Bug Reporting] alexxcons | contribute:bugs:start [2020/06/20 00:25] – Update links to https://gitlab.xfce.org andreldm | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bug Reporting | + | ====== Bug Reporting |
- | One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https://bugzilla.xfce.org|bug tracker]]. | + | One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https://gitlab.xfce.org|issue tracker]]. |
- | + | ||
- | ===== Fixing Bugs ===== | + | |
- | + | ||
- | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | + | |
- | + | ||
- | Not familiar with git? [[contribute/ | + | |
- | + | ||
- | After you managed to download the source code, check [[: | + | |
- | ===== Feature Requests ===== | + | |
- | + | ||
- | Although the philosophy of Xfce is to find the correct balance between features and lightweight, | + | |
- | + | ||
- | This right approach for larger changes is to discuss them on the mailing list first. You might think your idea is brilliant, but there is a high possibility other users. | + | |
- | + | ||
- | Afterwards a bug can be opened in the bug tracker and make sure the // | + | |
- | + | ||
- | Obviously its also nice if you can write a patch that implements the feature, but its not a necessity. | + | |
===== Crashes ===== | ===== Crashes ===== | ||
Line 27: | Line 10: | ||
==== Search First ==== | ==== Search First ==== | ||
- | Search the [[https://bugzilla.xfce.org|bug tracker]] and look if the issue is already known. Also look through the resolved bugs because the issue might be fixed already, but has not been released or applied downstream. Peeking the [[http://git.xfce.org/xfce|GIT repository]] might help for the latter. | + | Search the [[https://gitlab.xfce.org|issue tracker]] and look if the issue is already known. Also look through the resolved bugs because the issue might be fixed already, but has not been released or applied downstream. Peeking the [[https://gitlab.xfce.org|GIT repository]] might help for the latter. |
==== Report ==== | ==== Report ==== | ||
Line 54: | Line 37: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | |||
+ | ===== Fixing Bugs ===== | ||
+ | |||
+ | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | ||
+ | |||
+ | Not familiar with git? [[contribute/ | ||
+ | |||
+ | To get started, best read our [[contribute/ | ||
+ |