• BugReporting

English Version is here DebianEdu/BugReporting

Die Linux Distribution SkoleLinux basiert auf Debian. DebianEdu ist ein Produkt der Arbeit der Skolelinux community!

Aber SkoleLinux ist unabhängig, so dass einige Pakete neuer sind als die offiziellen Debian Versionen, manche sind älter, und manche sind ein Bisschen an die besonderen SkoleLinux Ansprüche angepasst.

Bugs sollten dem Debian Bugtracking System (BTS) gemeldet werden, um die erforderliche Koordination zur Lösung zu minimieren.

Manche Debian Verfechter lieben Feedback, selbst wenn es von externer Benutzung ihres Paketes abgeleitet wurde. Andere wollen sich nur direkt mit Debian befassen.

• Nutzen Sie Debian BTS für Debian Pakete die durch DebianEdu gewartet werden

• Nutzen Sie Debian BTS für Debian Pakete die in SkoleLinux unverändert angewendet werden

• Nutzen Sie Debian BTS für Debian Pakete die für SkoleLinux neu gebaut wurden, wenn der Ersteller des Debian Paketes solche Bug Meldungen annimmt

• Nutzen Sie SkoleLinux BTS für Debian Pakete die für SkoleLinux neu gebaut wurden, wenn der Paketersteller nicht explizit an solchen Bug Meldungen interessiert ist.

• Nutzen Sie SkoleLinux BTS für reine SkoleLinux Pakete.

Im Zweifelsfall sollte man einen Bug bei Skolelinux BTS melden.

Und hier eine Anleitung aus einer E-Mail von JonasSmedegaard:

>>> For Debian packages or as upstream bug tracker?
>>
>> For Debian.
>
>OK for Debian, no problem at all. (I guess)
>
>>> I probably prefer to have a small bug tracker for upstream. But 
>>> convince me to use a full blown up bug tracker on Debian, or do I 
>>> have a wrong impression?
>>
>> No no, I would certainly encourage you to use a small one upstream.
>
>OK ok. Then I can not see a reason why not using the Debian BTS for 
>Debian Packages.
>
>Are there any?

Sorry, I lost you above.  Let me try to describe a bug handling which 
makes the best sense to me:

Each role report bugs to their nearest upstream:

  * Users report to their admin
  * Admins report to their deployer (if not same person/team)
  * Deployers report to their distribution or alternate upstream
  * Distributions report to their upstream

...or more specifically:

  * RLP teachers/pupils report to the admin teacher
  * Admin teachers report to their supporter
  * Supporters report bugs in RLP images to RLP developers
  * Supporters report bugs in self-added .deb packages to Debian
  * Supporters report bugs in self-added CPAN modules to CPAN
  * Supporters report bugs in self-added CipUX SVN modules to CipUX
  * RLP developers report bugs in .deb packages to Debian
  * RLP developers report bugs in CPAN modules to CPAN
  * RLP developers report bugs in CipUX SVN modules to CipUX
  * Debian package maintainers report bugs in CPAN modules to CPAN
  * Debian package maintainers report bugs in CipUX tarballs to CipUX

All are welcome to additionally report to other places further upstream, 
but are recommended to a) always report to the nearest, and b) inform 
all that they involve about all others that they also involve.

Example: If a teacher happen to know how to report problems to Debian 
then it is great if she reports to *both* her supporter and to Debian, 
and make sure to mention at both places about the other getting reports 
too.

Reporting furhter up the chain without involving the "middle men" is 
discouraged, however, as that can potentially cause confusion and/or 
frustrations and lead to slower progress!

Use the issue tracker favored by your particular upstream:

  * Admin teachers use whatever tool they prefer or their boss decide
  * Supporters use whatever tool they prefer or their contract mandates
  * RLP developers use whatever tool they prefer
  * Debian uses their own BTS: http://bugs.debian.org/
  * CPAN uses Request Tracker: http://rt.cpan.org/
  * CipUX can use whatever tool you prefer, or loose notes, i.e. no 
    system


>> Have a look at bugs-everywhere - it is packaged for Debian (I can try 
>> backport it to stable if needed), upstream is here: 
>> http://bugseverywhere.org/
>>
>> Another alternative - even smaller and also distributed - is ticgit.
>> Also packaged for Debian, upstream is here:
>> http://wiki.github.com/schacon/ticgit

Above are my suggestions for simple yet distributed bug tracking.

You can also choose to do no project-specific bug tracking, and just 
rely on your downstreams to track all issues for you - but I recommend 
to not do that, since each downstream (Debian included!) is 
self-centered so tend to only track what hurts their particular users.


Hope that clarifies :-)


  - Jonas