X2Go - everywhere@home

User Tools

Site Tools

Trace:
wiki:bugs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
wiki:bugs [2013/03/14 20:19]
sunweaver 		wiki:bugs [2024/08/02 09:09] (current)
gratuxri [X2Go Bug Tracker]
Line 1: Line 1:
 ====== X2Go Bug Tracker ====== ====== X2Go Bug Tracker ======
  
-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.+Please use gitlab bug tracker at https://gitlab.x2go.org/ for any new bug reports or for viewing current bugs. Please login to [[https://gitlab.x2go.org/users/sign_in|gitlab]] once with your GitLab.com account. Then you need to request access first via the x2go-user mailing list. See [[contact:start|Overview on X2Go Community Communication]]
  
-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. +====== Viewing Bug History ======
- +
-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. +
- +
-===== Open / Closed Bugs =====+
  
 +For historical reasons you can access the previous bugtracker as described below. All (relevant) bugs have been moved to gitlab. 
  
 If you know either the X2Go component or the bug number you can also access the information directly: If you know either the X2Go component or the bug number you can also access the information directly:
  
-  * [[http://bugs.x2go.org/<nnn>]] (where <nnn> is the bug number) +http://bugs.x2go.org/<nnn> (where <nnn> is the bug number) 
-  * [[http://bugs.x2go.org/<x2go-component]] (where <x2go-component is a valid X2Go component) +http://bugs.x2go.org/<x2go-component> (where <x2go-component is a valid X2Go component)
 A complete list of X2Go components with open/closed bugs can be viewed with this URL: A complete list of X2Go components with open/closed bugs can be viewed with this URL:
  
-  * [[http://bugs.x2go.org/cgi-bin/pkgindex.cgi?indexon=src]] +http://bugs.x2go.org/cgi-bin/pkgindex.cgi?indexon=src
- +
-===== Reporting Bugs ===== +
- +
-How to report a bug is explained [[http://bugs.x2go.org/Reporting.html|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. +
- +
-<code> +
-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> +
-""" +
-</code> +
- +
-===== Controlling Bugs ===== +
- +
-The full control command set is documented [[http://bugs.x2go.org/server-control.html|here]]. +
- +
-Very common control sequence are shown below: +
- +
-==== Bug has been fixed in X2Go Git ==== +
- +
-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: +
- +
-<code> +
-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> +
-""" +
-</code> +
- +
-==== New version with a bug fixed has been released ==== +
- +
-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. +
- +
-<code> +
-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> +
-""" +
-</code> +
- +
-==== Bug has been reported against the wrong X2Go Component ==== +
- +
-Even for X2Go power-users and developers it is not always easy to tell, what X2Go component causes a certain buggy behaviour in X2Go. Once a problem has been narrowed down, we might need to reassign a bug to another X2Go component. +
- +
-<code> +
-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> +
-""" +
-</code> +
- +
- +
-==== Bug submitter used a non-appropriate title ==== +
- +
-<code> +
-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> +
-""" +
-</code> +
- +
- +
wiki/bugs.1363292356.txt.gz · Last modified: 2013/03/14 20:19 by sunweaver

Page Tools

Imprint & Legal Disclaimer - Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki