This is an old revision of the document!
The X2Go project uses the debbugs
as bug tracking system (BTS) software. The debbugs
tracker is the software that's also used by the Debian project for tracking issues in the multitude of Debian packages.
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' mail clients. Furthermore, we did not want a bug tracker that could be fed with content by clicking around on a web page.
The choice has been well thought of, you may find that there are better bug tracking systems in the world. For X2Go, we think we have found what we wanted.
If you know either the X2Go component or the bug number you can also access the information directly:
A complete list of X2Go components with open/closed bugs can be viewed with this URL:
How to report a bug is explained here. In a nutshell send a mail like the one below (everything that is written in <pointed-brackets> needs being replaced by some proper value.
To: submit@bugs.x2go.org Subject: <a-really-good-short-description-of-the-problem> Body: """ Package: <name-of-x2go-component> Version: <a.b.c.d> """
The full control command set is documented here.
Very common control sequence are shown below:
Bugs are only closed on releases of X2Go components. To mark a bug as fixed whilst it is not yet included in a release, we tag the bug as pending:
To: <nnn>@bugs.x2go.org Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org Subject: Issue resolved in X2Go Git Body: """ tag #<nnn> pending thanks The reported issue has been resolved with this commit: <http-URL-to-Gitweb-of-commitdiff> Thanks, <my-name> """
As part of the X2Go release workflow, bugs that have been fixed for this release have to be closed. Normally, most bugs are already marked (tagged) as pending.
Some pending bugs, though, may only have been fixed on the master branch, but not yet on a release branch. If the release is taken from a release branch, take a look at the released component's changelog before closing bugs that are not yet to be closed.
To: <nnn>@bugs.x2go.org Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org Subject: Issue resolved in <x2go-component> <version> Body: """ close #<nnn> thanks The reported issue has been resolved in the lately release version <version> of <x2go-component>. Thanks for reporting this issue, <my-name> """
To: <nnn>@bugs.x2go.org Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org Subject: <a-good-subject-line> Body: """ reassign #<nnn> <another-x2go-component> thanks The reported issue is actually a bug in <another-x2go-component>. Reassigning. <further-info-if-any> Thanks for reporting this issue, <my-name> """
To: <nnn>@bugs.x2go.org Cc: control@bugs.x2go.org, <nnn>-submitter@bugs.x2go.org Subject: <a-good-subject-line> Body: """ retitle #<nnn> <better-title> thanks <further-info-if-any> Thanks for reporting this issue, <my-name> """