Reporting bugs/de: Difference between revisions

Revision as of 21:22, 12 June 2018

Other languages:

Wichtig

Please, make bug reports to our issue tracker, so they won't get lost on forums or chatroom logs.
You can easily access it using Miranda: Main menu → Help → Report bug.
If you are unsure about the problem or want to bring more attention to it, you can mention it on our forum or chatroom too.

We want Miranda as bug free as you do, so help us help you. The most important thing to remember when reporting bugs is to provide complete and accurate information. Most of our time is spent asking for more information and fixing/updating information. So if you report a bug, please take the time to read and follow these recommendations.

Before reporting a bug

Update to the latest development version (see Updating Miranda NGInstallation and update).
Check if the problem persists (it may happen that it has been fixed).
Search the issues for an existing bug report for your problem.

Effective bug reporting

Screen 1: Creating issue

Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.

Have a well-written bug Title field – describe the issue clearly, in simple words.
Provide step-by-step instructions in Description field so we can reproduce the issue (We can't fix what we can't reproduce).
Attach screenshots if possible.
Attach your VersionInfoVersion information.
Attach a crash reportCrash reports if you are experiencing crashes (It includes VersionInfo as well).
Attach a network logNetwork log captured if you are experiencing connectivity issues.
If Miranda freezes, hangs up or consumes CPU, attach information obtained by Process Explorer tool.

How to attach files

Attach files by dragging & dropping, selecting them, or pasting from the clipboard
Press Submit new issue (see Screen 1).

I know when it got broken

If you know things got broken in some version or at some particular time, then it's good because you can try different releases from different revisions and narrow down where exactly the problem started to happen:

You can either compile the revisions yourself (that requires more knowledge and time).
Or ask someone in our jabber conference to help you identify potentially problematic revisions and then ask to compile those revisions for you.

Then you can try to reproduce your problem on each of them and find out when exactly it got broken. With that info it's easy to reach out the developer who commited the broken commit and ask him to look at it.

After reporting an issue

Monitor the issues you report.
Provide feedback and additional information if requested.
Don't argue about whether something is a bug or not.

@@ Line 1: / Line 1: @@
-* Bitte, machen Sie Fehlermeldungen auf unserem [https://github.com/miranda-ng/miranda-ng/issues Tracker] in '''englisch''', damit sie im Forum und unseren Chatverläufen nicht verloren gehen.
+<languages/>
-* Wenn Sie sich unsicher über ein Problem sind oder Sie mehr Aufmerksamkeit darauf lenken wollen, dann nutzen Sie bitte [https://forum.miranda-ng.org unser Forum] (auch deutsch) oder unseren [xmpp:miranda-ng-int@conference.jabber.ru?join Chatroom].
+{{TNT|Important|
+* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues issue tracker], so they won't get lost on forums or chatroom logs.<br>You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}.
+* If you are unsure about the problem or want to bring more attention to it, you can mention it on [https://forum.miranda-ng.org our forum] or [xmpp:miranda-ng-int@conference.jabber.ru?join chatroom] too.}}
-Wir wollen Miranda NG so fehlerfrei wie Sie. Wir sind bei Fehlern auf Ihre Mithilfe angewiesen. Nur so können wir Miranda NG noch besser machen. Wenn Sie einen Fehler in Miranda NG bemerken dann beachten Sie bitte folgende Informationen:
+We want Miranda as bug free as you do, so help us help you. The most important thing to remember when reporting bugs is to provide {{Strong|complete}} and {{Strong|accurate}} information. Most of our time is spent asking for more information and fixing/updating information. So if you report a bug, please take the time to read and follow these recommendations.
-== Bevor Sie einen Fehler melden ==
+__TOC__
-* Aktualisieren Sie Miranda NG auf die neuste Version (siehe [[Installation und Update]]).
+== Before reporting a bug ==
-* Prüfen Sie, ob der Fehler erneut auftritt (er könnte schon behoben worden sein).
-* Schauen Sie, ob im [https://github.com/miranda-ng/miranda-ng/issues Tracker] schon eine Fehlermeldung zu Ihrem Problem existiert.
-* Wenn Sie sich unsicher sind, ob etwas ein Fehler ist oder nicht, fragen Sie bitte im [https://forum.miranda-ng.org Forum] nach.
-== Fehler melden ==
+* Update to the latest {{GlossLink|development version}} (see {{Ll|Installation and update#Updating Miranda NG|Updating Miranda NG}}).
+* Check if the problem persists (it may happen that it has been fixed).
+* Search the [https://github.com/miranda-ng/miranda-ng/issues issues] for an existing bug report for your problem.
-Bild 1
+== Effective bug reporting ==
-Wenn Sie einen neuen Fehler melden dann beachten Sie bitte folgende Hinweise:
+[[File:Reporting bugs 01.png|200px|thumb|Screen 1: Creating issue]]
-* Sie müssen sich auf dem [https://github.com/miranda-ng/miranda-ng/issues Tracker] registrieren und anmelden.
-* Fehlerberichte bitte nur auf Englisch verfassen. Nicht alle Entwickler sprechen Deutsch.
-* Geben Sie im Feld <tt>Summary</tt> eine '''aussagekräftige''' kurze Zusammenfassung des Problems ein.
-* Beschreiben Sie den Fehler in klaren, verständlichen Worten.
-* Geben Sie eine Schritt-für-Schritt-Anleitung an, wie man den Fehler reproduzieren kann. Das ist sehr wichtig.
-* Fügen Sie gegebenenfalls Screenshots an.
-* Fügen Sie eine [[Versionsinformation]] an (als Anhang zu Ihrer Fehlermeldung).
-* Fügen Sie bei Anstürzen einen [[Crash-Report-Erstellung|Crash Report]] an (dieser beinhaltet eine Versionsinfo).
-* Fügen Sie bei Netzwerkfehlern einen [[Netzwerklog]] an.
-* Wenn Miranda NG sich aufhängt, einfriert oder zuviel CPU verbraucht, dann fügen Sie die [[Process Explorer als Debugging-Tool verwenden|Informationen vom Process Explorer]] ein.
-=== Wie man Dateien anfügt ===
+Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.
-* Fügen Sie Dateien per Drag and Drop an oder fügen Sie sie aus Zwischenablage ein oder klicken Sie auf "selecting them" um die Dateien zum Anfügen auszuwählen (Bild 1).
+* Have a well-written bug Title field – describe the issue clearly, in simple words.
-* Klicken Sie auf {{Button|Submit new issue}}.
+* Provide step-by-step instructions in Description field  so we can reproduce the issue (''We can't fix what we can't reproduce'').
+* Attach screenshots if possible.
+* Attach your {{Ll|Version information|VersionInfo}}.
+* Attach a {{Ll|Crash reports|crash report}} if you are experiencing crashes (It includes VersionInfo as well).
+* Attach a {{Ll|Network log|network log}} captured if you are experiencing connectivity issues.
+* If Miranda freezes, hangs up or consumes CPU, attach {{Ll|Using Process Explorer as the debugging tool|information obtained by Process Explorer tool}}.
-== Nachdem Sie den Fehler gemeldet haben ==
+=== How to attach files ===
-* Beobachen Sie Ihre Fehlermeldung für Rückfragen der Entwickler.
+* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
-* Reichen Sie gegebenenfalls fehlende Informationen nach.
+* Press {{Button|Submit new issue}} (see Screen 1).
-* Diskutieren Sie nicht, ob etwas ein Fehler ist oder nicht.
+== I know when it got broken ==
+If you know things got broken in some version or at some particular time, then it's good because you can try different releases from different revisions and narrow down where exactly the problem started to happen:
+* You can either compile the revisions yourself (that requires more knowledge and time).
+* Or ask someone in our [xmpp:miranda-ng-int@conference.jabber.ru?join jabber conference] to help you identify potentially problematic revisions and then ask to compile those revisions for you.
+Then you can try to reproduce your problem on each of them and find out when exactly it got broken. With that info it's easy to reach out the developer who commited the broken commit and ask him to look at it.
+== After reporting an issue ==
+* Monitor the issues you report.
+* Provide feedback and additional information if requested.
+* Don't argue about whether something is a bug or not.
+[[Category:Help|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]