Reporting bugs/ru

Важно

• 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.

Сообщая об ошибке, важно предоставить полную и точную информацию о ней. На расспросы, выяснение подробностей и уточнение неполной информации уходит много времени. Поэтому перед тем как отправить баг-репорт, прочтите, пожалуйста, эти советы — они помогут вам сообщить об ошибке подробно и точно. Наш баг-трекер: https://github.com/miranda-ng/miranda-ng/issues На трекер можно перейти из Миранды: Главное меню → Справка → Сообщить об ошибке.

С чего начать

• Обновитесь до последней версии, находящейся в разработке (см. Обновление Miranda NGInstallation and update).
• Проверьте, появляется ли ошибка снова (Возможно, её уже исправили).
• Убедитесь, что на трекере нет сообщения о вашей ошибке.

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.