This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:bugs [2013/03/26 10:22] sunweaver [Bug submitter used a non-appropriate title] |
wiki:bugs [2014/08/04 17:17] sunweaver [Cloning bugs] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== X2Go Bug Tracker ====== | ====== X2Go Bug Tracker ====== | ||
- | The X2Go project uses the '' | + | The X2Go project uses '' |
Before X2Go had a bug tracker, the quest was: we need a BTS that is easily scriptable and a BTS that fully maps issue tracking to the developers' | Before X2Go had a bug tracker, the quest was: we need a BTS that is easily scriptable and a BTS that fully maps issue tracking to the developers' | ||
Line 28: | Line 28: | ||
Subject: < | Subject: < | ||
Body: | Body: | ||
- | """ | ||
Package: < | Package: < | ||
Version: < | Version: < | ||
< | < | ||
- | """ | ||
</ | </ | ||
Line 39: | Line 37: | ||
In case you can provide a patch with your bug report, please attach the patch to your bug report. Do __not__ copy+paste the patch into the mail body, as the result will not be usable!!! | In case you can provide a patch with your bug report, please attach the patch to your bug report. Do __not__ copy+paste the patch into the mail body, as the result will not be usable!!! | ||
+ | |||
+ | Create patches for master branch and send them in git format. The documentation about creating git patches can be found [[http:// | ||
Some of you have their own Git clones of X2Go Git. If you want to provide a patch via your public Git clone of an X2Go component, please make sure that the patch is just one commit on one of your Git branches. The rule here is simple: one Git commit on your side, one bug report in X2Go BTS. Everything else will take too much time on the patch reviewer side. | Some of you have their own Git clones of X2Go Git. If you want to provide a patch via your public Git clone of an X2Go component, please make sure that the patch is just one commit on one of your Git branches. The rule here is simple: one Git commit on your side, one bug report in X2Go BTS. Everything else will take too much time on the patch reviewer side. | ||
Line 48: | Line 48: | ||
Subject: < | Subject: < | ||
Body: | Body: | ||
- | """ | ||
Package: < | Package: < | ||
Version: < | Version: < | ||
Line 54: | Line 53: | ||
< | < | ||
- | """ | + | |
Attachment: < | Attachment: < | ||
</ | </ | ||
+ | |||
+ | ==== Feature requests / Wishlist bugs ==== | ||
+ | |||
+ | Feature requests are also handled via the X2Go BTS system. Feature requests are bugs with severity ,, | ||
+ | |||
+ | < | ||
+ | To: submit@bugs.x2go.org | ||
+ | Subject: < | ||
+ | Body: | ||
+ | Package: < | ||
+ | Version: < | ||
+ | Severity: wishlist | ||
+ | |||
+ | < | ||
+ | </ | ||
+ | |||
Line 67: | Line 82: | ||
==== Bug has been fixed in X2Go Git ==== | ==== Bug has been fixed in X2Go Git ==== | ||
- | Bugs are only closed as part of the X2Go release workflow. The release manager only is allowed to close bugs (this is an agreement, not a technical constraint). To mark a bug as fixed whilst it is not yet included | + | Marking |
- | < | + | **Important notice for developers:** Every X2Go source project uses ''/ |
- | To: < | + | |
- | Cc: control@bugs.x2go.org, | + | |
- | Subject: Issue resolved in X2Go Git | + | |
- | Body: | + | |
- | """ | + | |
- | tag #< | + | |
- | fixed #< | + | |
- | thanks | + | |
- | + | ||
- | The reported issue has been resolved with this commit: | + | |
- | < | + | |
- | + | ||
- | Thanks, | + | |
- | < | + | |
- | """ | + | |
- | </ | + | |
==== New version with a bug fixed has been released ==== | ==== New version with a bug fixed has been released ==== | ||
Line 95: | Line 94: | ||
< | < | ||
To: < | To: < | ||
- | Cc: control@bugs.x2go.org, | + | Cc: < |
Subject: Issue resolved in < | Subject: Issue resolved in < | ||
Body: | Body: | ||
- | """ | + | Control: |
- | close #< | + | |
- | thanks | + | |
The reported issue has been resolved in the lately release version < | The reported issue has been resolved in the lately release version < | ||
Line 106: | Line 103: | ||
Thanks for reporting this issue, | Thanks for reporting this issue, | ||
< | < | ||
- | """ | ||
</ | </ | ||
Line 115: | Line 111: | ||
< | < | ||
To: < | To: < | ||
- | Cc: control@bugs.x2go.org, | + | Cc: < |
Subject: < | Subject: < | ||
Body: | Body: | ||
- | """ | + | Control: |
- | reassign | + | |
- | thanks | + | |
The reported issue is actually a bug in < | The reported issue is actually a bug in < | ||
Line 128: | Line 122: | ||
Thanks for reporting this issue, | Thanks for reporting this issue, | ||
< | < | ||
- | """ | ||
</ | </ | ||
Line 138: | Line 131: | ||
< | < | ||
To: < | To: < | ||
- | Cc: control@bugs.x2go.org, | + | Cc: < |
Subject: < | Subject: < | ||
Body: | Body: | ||
- | """ | + | Control: |
- | retitle | + | |
- | thanks | + | |
< | < | ||
Line 162: | Line 153: | ||
Subject: < | Subject: < | ||
Body: | Body: | ||
- | """ | ||
clone #< | clone #< | ||
tag -1 - pending | tag -1 - pending | ||
+ | tag -1 - patch | ||
reassign -1 < | reassign -1 < | ||
retitle #< | retitle #< | ||
Line 173: | Line 164: | ||
Best, | Best, | ||
< | < | ||
- | """ | ||
</ | </ | ||