Reporting bugs/ru: Difference between revisions

Revision as of 21:22, 12 June 2018

Other languages:

Важно

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: @@
-Сообщая об ошибке, важно предоставить '''полную''' и '''точную''' информацию о ней. На расспросы, выяснение подробностей и уточнение неполной информации уходит много времени. Поэтому перед тем как отправить {{GlossLink|Баг-репорт|баг-репорт}}, прочтите, пожалуйста, эти советы — они помогут вам сообщить об ошибке подробно и точно. Наш баг-трекер: https://github.com/miranda-ng/miranda-ng/issues На трекер можно перейти из Миранды: {{Menu|Главное меню|Справка|Сообщить об ошибке}}.
+<languages/>
+{{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.}}
-== С чего начать ==
+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.
-* Обновитесь до последней {{GlossLink|Версия в разработке|версии, находящейся в разработке}} (см. [[Установка и обновление#Обновление Miranda NG|Обновление Miranda NG]]).
+__TOC__
-* Проверьте, появляется ли ошибка снова (Возможно, её уже исправили).
-* Убедитесь, что на [https://github.com/miranda-ng/miranda-ng/issues трекере] нет сообщения о вашей ошибке.
-== Сообщение об ошибке ==
+== Before reporting a bug ==
-Рис. 1
+* 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.
-* Чтобы отправить новое сообщение об ошибке, необходимо зарегистрироваться на трекере и выполнить вход.
+== Effective bug reporting ==
-* Составляйте баг-репорты на английском языке, не все разработчики владеют русским.
-* Кратко сформулируйте суть проблемы в заголовке (<tt>Summary</tt>). Отнеситесь внимательно к заполнению этого поля — его нельзя будет редактировать позже.
-* <tt>Description</tt> — подробно опишите проблему понятными словами. Укажите последовательность действий для воспроизведения ошибки (Эта часть баг-репорта самая важная: нельзя исправить то, что невозможно воспроизвести).
-* Сделайте и приложите скриншот.
-* Создайте и приложите [[Информация о версиях|отчёт VersionInfo]].
-* Если Миранда «падает», создайте и приложите [[Создание краш-репортов|краш-репорт]] (содержит также VersionInfo).
-* Если у вас проблемы с подключением, создайте и приложите [[Создание сетевых логов|сетевой лог]].
-* Если Миранда подвисает или начинает потреблять CPU, приложите [[Process Explorer в качестве инструмента отладки|информацию программы Process Explorer]].
-=== Как приложить файл ===
+[[File:Reporting bugs 01.png|200px|thumb|Screen 1: Creating issue]]
-* Добавляйте файлы перетаскиванием или вставляйте из буфера обмена, или нажмите ссылку ''«selecting them»'', чтобы выбрать файл на компьютере (рис. 1).
+Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.
-* Нажмите {{Button|Submit new issue}}.
-== Что делать потом ==
+* 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 {{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}}.
-* Следите за своим сообщением.
+=== How to attach files ===
-* Отвечайте на вопросы и предоставляйте дополнительную информацию.
-* Не спорьте, является ваша проблема ошибкой или нет.
+* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
+* Press {{Button|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 [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}}}}]]