Reporting bugs/be: Difference between revisions

From Miranda NG
Reporting bugs/be
Jump to navigation Jump to search
(prepare for migration)
(Updating to match new version of source page)
Line 1: Line 1:
Паведамляючы пра памылку, важна падаць '''поўную''' і '''дакладную''' інфармацыю пра яе. На роспыты, высвятленне падрабязнасцяў і ўдакладненне няпоўнай інфармацыі сыходзіць шмат часу. Таму перад тым як адправіць баг-рэпорт, прачытайце, калі ласка, гэтыя рады — яны дапамогуць вам паведаміць пра памылку падрабязна і сапраўды. Наш баг-трэкер: 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 ==


[[File:Reporting bugs 01.png|200px|thumb|Мал. 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).
* Калі ў вас праблемы з далучэннем, стварыце і прыкладзіце [[Стварэнне сеткавых логаў|сеткавы лог]].


=== Як прыкласці файл ===
[[File:Reporting bugs 01.png|200px|thumb|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 {{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}}}}]]

Revision as of 21:21, 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

Effective bug reporting

Screen 1: Creating issue

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

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.
Retrieved from "https://wiki.miranda-ng.org/index.php?title=Reporting_bugs/be&oldid=31092"