Reporting bugs/pl

Ważne

• Proszę zgłaszaj błędy na nasz bug tracker, by nie zaginęły one gdzieś na forum lub czacie.
  Możesz łatwo uzyskać do niego dostęp z menu Mirandy: Menu główne → Pomoc → Zgłoś błąd.
• Jeżeli nie jesteś pewny co do błędu lub chcesz zwrócić na niego większą uwagę, możesz także o nim wspomnieć na naszym forum i/lub czacie.

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 toolUsing Process Explorer as the debugging 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.