Reporting bugs - Revision history

Goraf: add language independent anchor for 'Effective bug reporting'

2018-06-13T07:59:32Z

add language independent anchor for 'Effective bug reporting'

← Older revision		Revision as of 10:59, 13 June 2018
Line 21:		Line 21:
	* Check if the problem persists (it may happen that it has been fixed).		* Check if the problem persists (it may happen that it has been fixed).
	* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.		* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.
			</translate>

			{{Anchor\|Effective bug reporting}}
			<translate>
	== Effective bug reporting == <!--T:5-->		== Effective bug reporting == <!--T:5-->
	</translate>		</translate>

Goraf: fix categorization

2018-06-12T19:17:59Z

fix categorization

← Older revision		Revision as of 22:17, 12 June 2018
Line 66:		Line 66:
	</translate>		</translate>

	[[Category:Help\|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]		[[Category:Help{{#translation:}}\|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Goraf: Marked this version for translation

2018-06-12T18:21:41Z

Marked this version for translation

← Older revision		Revision as of 21:21, 12 June 2018
Line 2:		Line 2:
	{{TNT\|Important\|		{{TNT\|Important\|
	<translate>		<translate>
			<!--T:1-->
	* Please, make bug reports to our [<tvar\|github_tracker_url>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}}.		* Please, make bug reports to our [<tvar\|github_tracker_url>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 [<tvar\|forum_url>https://forum.miranda-ng.org</> our forum] or [<tvar\|jabber_chatroom_url>xmpp:miranda-ng-int@conference.jabber.ru?join</> chatroom] too.		* If you are unsure about the problem or want to bring more attention to it, you can mention it on [<tvar\|forum_url>https://forum.miranda-ng.org</> our forum] or [<tvar\|jabber_chatroom_url>xmpp:miranda-ng-int@conference.jabber.ru?join</> chatroom] too.
Line 7:		Line 8:

	<translate>		<translate>
			<!--T:2-->
	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.		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.
	</translate>		</translate>
Line 13:		Line 15:

	<translate>		<translate>
	== Before reporting a bug ==		== Before reporting a bug == <!--T:3-->

			<!--T:4-->
	* Update to the latest {{GlossLink\|development version}} (see {{Ll\|Installation and update#Updating Miranda NG\|Updating Miranda NG}}).		* 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).		* Check if the problem persists (it may happen that it has been fixed).
	* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.		* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.

	== Effective bug reporting ==		== Effective bug reporting == <!--T:5-->
	</translate>		</translate>

	[[File:Reporting bugs 01.png\|200px\|thumb\|<translate>Screen 1: Creating issue</translate>]]		[[File:Reporting bugs 01.png\|200px\|thumb\|<translate><!--T:6--> Screen 1: Creating issue</translate>]]

	<translate>		<translate>
			<!--T:7-->
	Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.		Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.

			<!--T:8-->
	* Have a well-written bug <tvar\|title_field>Title</> field – describe the issue clearly, in simple words.		* Have a well-written bug <tvar\|title_field>Title</> field – describe the issue clearly, in simple words.
	* Provide step-by-step instructions in <tvar\|description_field>Description</> field so we can reproduce the issue (''We can't fix what we can't reproduce'').		* Provide step-by-step instructions in <tvar\|description_field>Description</> field so we can reproduce the issue (''We can't fix what we can't reproduce'').
Line 35:		Line 40:
	* If Miranda freezes, hangs up or consumes CPU, attach {{Ll\|Using Process Explorer as the debugging tool\|information obtained by Process Explorer tool}}.		* 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 ===		=== How to attach files === <!--T:9-->

			<!--T:10-->
	* Attach files by dragging & dropping, selecting them, or pasting from the clipboard		* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
	* Press <tvar\|submit_button>{{Button\|Submit new issue}}</> (see Screen 1).		* Press <tvar\|submit_button>{{Button\|Submit new issue}}</> (see Screen 1).

	== I know when it got broken ==		== I know when it got broken == <!--T:11-->

			<!--T:12-->
	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:		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:

			<!--T:13-->
	* You can either compile the revisions yourself (that requires more knowledge and time).		* You can either compile the revisions yourself (that requires more knowledge and time).
	* Or ask someone in our [<tvar\|jabber_chatroom_url>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.		* Or ask someone in our [<tvar\|jabber_chatroom_url>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.

			<!--T:14-->
	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.		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 ==		== After reporting an issue == <!--T:15-->

			<!--T:16-->
	* Monitor the issues you report.		* Monitor the issues you report.
	* Provide feedback and additional information if requested.		* Provide feedback and additional information if requested.

Goraf: remove old langabar

2018-06-12T18:21:24Z

remove old langabar

← Older revision		Revision as of 21:21, 12 June 2018
Line 1:		Line 1:
	<languages/>~~{{PageLang\|en}}{{Languages/Report bug}}~~		<languages/>
	{{TNT\|Important\|		{{TNT\|Important\|
	<translate>		<translate>

Goraf: use localized links; add sort key for category; remove deprecated in HTML5 `; use semantically correct emphasis`

2018-06-12T18:05:17Z use localized links; add sort key for category; remove deprecated in HTML5 <tt>; use semantically correct emphasis ← Older revision Revision as of 21:05, 12 June 2018 Line 7: Line 7: <translate> <translate> 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. 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. </translate> </translate> __TOC__ __TOC__ Line 16: Line 15: == Before reporting a bug == == Before reporting a bug == * Update to the latest {{GlossLink|development version}} (see [[Installation and update#Updating Miranda NG|Updating Miranda NG]]). * 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). * Check if the problem persists (it may happen that it has been fixed). * Search the [<tvar|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem. * Search the [<tvar|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem. Line 26: Line 25: <translate> <translate> Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly. * Have a well-written bug <tvar|title_field><tt>Title</tt></> field – describe the issue clearly, in simple words. * Have a well-written bug <tvar|title_field>Title</> field – describe the issue clearly, in simple words. * Provide step-by-step instructions in <tvar|description_field><tt>Description</tt></> field so we can reproduce the issue (''We can't fix what we can't reproduce''). * Provide step-by-step instructions in <tvar|description_field>Description</> field so we can reproduce the issue (''We can't fix what we can't reproduce''). * Attach screenshots if possible. * Attach screenshots if possible. * Attach your [[version information|VersionInfo]]. * Attach your {{Ll|Version information|VersionInfo}}. * Attach a [[Crash reports|crash report]] if you are experiencing crashes (It includes VersionInfo as well). * Attach a {{Ll|Crash reports|crash report}} if you are experiencing crashes (It includes VersionInfo as well). * Attach a [[network log]] captured if you are experiencing connectivity issues. * Attach a {{Ll|Network log|network log}} captured if you are experiencing connectivity issues. * If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool|information obtained by Process Explorer tool]]. * 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 === === How to attach files === Line 57: Line 56: </translate> </translate> [[Category:Help]] [[Category:Help|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Goraf: split translation unit 2018-04-05T16:00:28Z split translation unit ← Older revision Revision as of 19:00, 5 April 2018 Line 43: Line 43: == I know when it got broken == == 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. 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 [<tvar|jabber_chatroom_url>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. * You can either compile the revisions yourself (that requires more knowledge and time). * Or ask someone in our [<tvar|jabber_chatroom_url>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. 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. Goraf: add translate tags and variables 2018-04-05T15:57:34Z add translate tags and variables ← Older revision Revision as of 18:57, 5 April 2018 Line 1: Line 1: {{PageLang|en}}{{Languages/Report bug}} <languages/>{{PageLang|en}}{{Languages/Report bug}} {{TNT|Important| {{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}}. <translate> * 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.}} * Please, make bug reports to our [<tvar|github_tracker_url>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 [<tvar|forum_url>https://forum.miranda-ng.org</> our forum] or [<tvar|jabber_chatroom_url>xmpp:miranda-ng-int@conference.jabber.ru?join</> chatroom] too. </translate>}} <translate> 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. 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. </translate> __TOC__ __TOC__ <translate> == Before reporting a bug == == Before reporting a bug == * Update to the latest {{GlossLink|development version}} (see [[Installation and update#Updating Miranda NG|Updating Miranda NG]]). * Update to the latest {{GlossLink|development version}} (see [[Installation and update#Updating Miranda NG|Updating Miranda NG]]). * Check if the problem persists (it may happen that it has been fixed). * 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. * Search the [<tvar|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem. == Effective bug reporting == == Effective bug reporting == </translate> [[File:Reporting bugs 01.png|200px|thumb|Screen 1: Creating issue]] [[File:Reporting bugs 01.png|200px|thumb|<translate>Screen 1: Creating issue</translate>]] <translate> Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. * Have a well-written bug <tt>Title</tt> field – describe the issue clearly, in simple words. * Have a well-written bug <tvar|title_field><tt>Title</tt></> field – describe the issue clearly, in simple words. * Provide step-by-step instructions in <tt>Description</tt> field so we can reproduce the issue (''We can't fix what we can't reproduce''). * Provide step-by-step instructions in <tvar|description_field><tt>Description</tt></> field so we can reproduce the issue (''We can't fix what we can't reproduce''). * Attach screenshots if possible. * Attach screenshots if possible. * Attach your [[version information|VersionInfo]]. * Attach your [[version information|VersionInfo]]. Line 32: Line 39: * Attach files by dragging & dropping, selecting them, or pasting from the clipboard * Attach files by dragging & dropping, selecting them, or pasting from the clipboard * Press {{Button|Submit new issue}} (see Screen 1). * Press <tvar|submit_button>{{Button|Submit new issue}}</> (see Screen 1). == I know when it got broken == == I know when it got broken == Line 38: Line 45: 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. 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) * 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. * or ask someone in our [<tvar|jabber_chatroom_url>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. 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. Line 47: Line 54: * Provide feedback and additional information if requested. * Provide feedback and additional information if requested. * Don't argue about whether something is a bug or not. * Don't argue about whether something is a bug or not. </translate> [[Category:Help]] [[Category:Help]] Goraf: Remove outdated parts 2018-04-05T12:45:57Z Remove outdated parts ← Older revision Revision as of 15:45, 5 April 2018 Line 1: Line 1: {{PageLang|en}}{{Languages/Report bug}} {{PageLang|en}}{{Languages/Report bug}} {{TNT|Important| {{TNT|Important| * Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs. * 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.}} * 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 '''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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}. 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. Line 17: Line 17: == Effective bug reporting == == Effective bug reporting == [[File:Reporting bugs 01.png|200px|thumb|Screen 1]] [[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. Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. * Have a well-written bug <tt>Summary</tt> field – describe the issue clearly, in simple words (''This is very important because you cannot edit it later''). * Have a well-written bug <tt>Title</tt> field – describe the issue clearly, in simple words. * <tt>Description</tt> field – provide step-by-step instructions so we can reproduce the issue (''We can't fix what we can't reproduce''). * Provide step-by-step instructions in <tt>Description</tt> field so we can reproduce the issue (''We can't fix what we can't reproduce''). * Attach screenshots if possible. * Attach screenshots if possible. * Attach your [[version information|VersionInfo]]. * Attach your [[version information|VersionInfo]]. Line 28: Line 28: * Attach a [[network log]] captured if you are experiencing connectivity issues. * Attach a [[network log]] captured if you are experiencing connectivity issues. * If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool|information obtained by Process Explorer tool]]. * If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool|information obtained by Process Explorer tool]]. * <tt>Type</tt> – select <tt>enhancement</tt> here if: ** you have a feature request ** you offer an improvement for something already implemented. * Specify the other elements of your report, such as: <tt>Priority</tt>, <tt>Severity</tt> (the importance of defect), Miranda <tt>Version</tt> and <tt>Component</tt>. You can also add <tt>Keywords</tt>. === How to attach files === === How to attach files === Goraf: Prepare for translation 2018-04-05T10:37:26Z Prepare for translation ← Older revision Revision as of 13:37, 5 April 2018 Line 1: Line 1: {{PageLang|en}}{{Languages/Report bug}} {{PageLang|en}}{{Languages/Report bug}} {{Important| {{TNT|Important| * Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs. * Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs. * 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.}} * 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 '''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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}. 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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}. Line 9: Line 10: == Before reporting a bug == == Before reporting a bug == * Update to the latest {{GlossLink|development version}} (see [[Installation and update#Updating Miranda NG|Updating Miranda NG]]). * Update to the latest {{GlossLink|development version}} (see [[Installation and update#Updating Miranda NG|Updating Miranda NG]]). * Check if the problem persists (it may happen that it has been fixed). * Check if the problem persists (it may happen that it has been fixed). Line 14: Line 16: == Effective bug reporting == == Effective bug reporting == [[File:Reporting bugs 01.png|200px|thumb|Screen 1]] [[File:Reporting bugs 01.png|200px|thumb|Screen 1]] Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly. Line 30: Line 34: === How to attach files === === How to attach files === * Attach files by dragging & dropping, selecting them, or pasting from the clipboard * Attach files by dragging & dropping, selecting them, or pasting from the clipboard * Press {{Button|Submit new issue}} (see Screen 1). * Press {{Button|Submit new issue}} (see Screen 1). == I know when it got broken == == 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. 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) * you can either compile the revisions yourself (that requires more knowledge and time) Line 41: Line 47: == After reporting an issue == == After reporting an issue == * Monitor the issues you report. * Monitor the issues you report. * Provide feedback and additional information if requested. * Provide feedback and additional information if requested. Dart Raiden at 00:37, 7 August 2017 2017-08-07T00:37:00Z ← Older revision Revision as of 03:37, 7 August 2017 Line 2: Line 2: {{Important| {{Important| * Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs. * Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs. * If you are unsure about the problem or want to bring more attention to it, you can mention it on [http://forum.miranda-ng.org our forum] or [xmpp:miranda-ng-int@conference.jabber.ru?join chatroom] too.}} * 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 '''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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}. 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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu|Main menu|Help|Report bug}}.

← Older revision		Revision as of 21:05, 12 June 2018
Line 7:		Line 7:

	<translate>		<translate>
	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.		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.
	</translate>		</translate>


	__TOC__		__TOC__
Line 16:		Line 15:
	== Before reporting a bug ==		== Before reporting a bug ==

	* Update to the latest {{GlossLink\|development version}} (see [[Installation and update#Updating Miranda NG\|Updating Miranda NG]]).		* 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).		* Check if the problem persists (it may happen that it has been fixed).
	* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.		* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.
Line 26:		Line 25:

	<translate>		<translate>
	Using the following tips will ~~'''~~greatly~~'''~~ increase the chances of your issue being ~~'''~~noticed~~'''~~ and ~~'''~~fixed~~'''~~ quickly.		Using the following tips will greatly increase the chances of your issue being noticed and fixed quickly.

	* Have a well-written bug <tvar\|title_field~~><tt~~>Title~~</tt>~~</> field – describe the issue clearly, in simple words.		* Have a well-written bug <tvar\|title_field>Title</> field – describe the issue clearly, in simple words.
	* Provide step-by-step instructions in <tvar\|description_field~~><tt~~>Description~~</tt>~~</> field so we can reproduce the issue (''We can't fix what we can't reproduce'').		* Provide step-by-step instructions in <tvar\|description_field>Description</> field so we can reproduce the issue (''We can't fix what we can't reproduce'').
	* Attach screenshots if possible.		* Attach screenshots if possible.
	* Attach your ~~[[version~~ information\|VersionInfo]].		* Attach your {{Ll\|Version information\|VersionInfo}}.
	* Attach a [[Crash reports\|crash report]] if you are experiencing crashes (It includes VersionInfo as well).		* Attach a {{Ll\|Crash reports\|crash report}} if you are experiencing crashes (It includes VersionInfo as well).
	* Attach a [[network log]] captured if you are experiencing connectivity issues.		* Attach a {{Ll\|Network log\|network log}} captured if you are experiencing connectivity issues.
	* If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool\|information obtained by Process Explorer tool]].		* 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 ===		=== How to attach files ===
Line 57:		Line 56:
	</translate>		</translate>

	[[Category:Help]]		[[Category:Help\|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

← Older revision		Revision as of 19:00, 5 April 2018
Line 43:		Line 43:
	== I know when it got broken ==		== 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.		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 [<tvar\|jabber_chatroom_url>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.		* You can either compile the revisions yourself (that requires more knowledge and time).
			* Or ask someone in our [<tvar\|jabber_chatroom_url>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.		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.

← Older revision		Revision as of 18:57, 5 April 2018
Line 1:		Line 1:
	{{PageLang\|en}}{{Languages/Report bug}}		<languages/>{{PageLang\|en}}{{Languages/Report bug}}
	{{TNT\|Important\|		{{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}}.		<translate>
	* 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.}}		* Please, make bug reports to our [<tvar\|github_tracker_url>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 [<tvar\|forum_url>https://forum.miranda-ng.org</> our forum] or [<tvar\|jabber_chatroom_url>xmpp:miranda-ng-int@conference.jabber.ru?join</> chatroom] too.
			</translate>}}

			<translate>
	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.		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.
			</translate>


	__TOC__		__TOC__

			<translate>
	== Before reporting a bug ==		== Before reporting a bug ==

	* Update to the latest {{GlossLink\|development version}} (see [[Installation and update#Updating Miranda NG\|Updating Miranda NG]]).		* Update to the latest {{GlossLink\|development version}} (see [[Installation and update#Updating Miranda NG\|Updating Miranda NG]]).
	* Check if the problem persists (it may happen that it has been fixed).		* 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.		* Search the [<tvar\|github_tracker_url>https://github.com/miranda-ng/miranda-ng/issues</> issues] for an existing bug report for your problem.

	== Effective bug reporting ==		== Effective bug reporting ==
			</translate>

	[[File:Reporting bugs 01.png\|200px\|thumb\|Screen 1: Creating issue]]		[[File:Reporting bugs 01.png\|200px\|thumb\|<translate>Screen 1: Creating issue</translate>]]

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

	* Have a well-written bug <tt>Title</tt> field – describe the issue clearly, in simple words.		* Have a well-written bug <tvar\|title_field><tt>Title</tt></> field – describe the issue clearly, in simple words.
	* Provide step-by-step instructions in <tt>Description</tt> field so we can reproduce the issue (''We can't fix what we can't reproduce'').		* Provide step-by-step instructions in <tvar\|description_field><tt>Description</tt></> field so we can reproduce the issue (''We can't fix what we can't reproduce'').
	* Attach screenshots if possible.		* Attach screenshots if possible.
	* Attach your [[version information\|VersionInfo]].		* Attach your [[version information\|VersionInfo]].
Line 32:		Line 39:

	* Attach files by dragging & dropping, selecting them, or pasting from the clipboard		* Attach files by dragging & dropping, selecting them, or pasting from the clipboard
	* Press {{Button\|Submit new issue}} (see Screen 1).		* Press <tvar\|submit_button>{{Button\|Submit new issue}}</> (see Screen 1).

	== I know when it got broken ==		== I know when it got broken ==
Line 38:		Line 45:
	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.		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)		* 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.		* or ask someone in our [<tvar\|jabber_chatroom_url>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.		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.
Line 47:		Line 54:
	* Provide feedback and additional information if requested.		* Provide feedback and additional information if requested.
	* Don't argue about whether something is a bug or not.		* Don't argue about whether something is a bug or not.
			</translate>

	[[Category:Help]]		[[Category:Help]]

← Older revision		Revision as of 15:45, 5 April 2018
Line 1:		Line 1:
	{{PageLang\|en}}{{Languages/Report bug}}		{{PageLang\|en}}{{Languages/Report bug}}
	{{TNT\|Important\|		{{TNT\|Important\|
	* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs.		* 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.}}		* 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 '''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~~. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu\|Main menu\|Help\|Report bug}}~~.		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.


Line 17:		Line 17:
	== Effective bug reporting ==		== Effective bug reporting ==

	[[File:Reporting bugs 01.png\|200px\|thumb\|Screen 1]]		[[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.		Using the following tips will '''greatly''' increase the chances of your issue being '''noticed''' and '''fixed''' quickly.

	* Have a well-written bug <tt>~~Summary~~</tt> field – describe the issue clearly, in simple words ~~(''This is very important because you cannot edit it later'')~~.		* Have a well-written bug <tt>Title</tt> field – describe the issue clearly, in simple words.
	* <tt>Description</tt> field ~~– provide step-by-step instructions~~ so we can reproduce the issue (''We can't fix what we can't reproduce'').		* Provide step-by-step instructions in <tt>Description</tt> field so we can reproduce the issue (''We can't fix what we can't reproduce'').
	* Attach screenshots if possible.		* Attach screenshots if possible.
	* Attach your [[version information\|VersionInfo]].		* Attach your [[version information\|VersionInfo]].
Line 28:		Line 28:
	* Attach a [[network log]] captured if you are experiencing connectivity issues.		* Attach a [[network log]] captured if you are experiencing connectivity issues.
	* If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool\|information obtained by Process Explorer tool]].		* If Miranda freezes, hangs up or consumes CPU, attach [[Using Process Explorer as the debugging tool\|information obtained by Process Explorer tool]].
	* <tt>Type</tt> – select <tt>enhancement</tt> here if:
	** you have a feature request
	** you offer an improvement for something already implemented.
	* Specify the other elements of your report, such as: <tt>Priority</tt>, <tt>Severity</tt> (the importance of defect), Miranda <tt>Version</tt> and <tt>Component</tt>. You can also add <tt>Keywords</tt>.

	=== How to attach files ===		=== How to attach files ===

← Older revision		Revision as of 13:37, 5 April 2018
Line 1:		Line 1:
	{{PageLang\|en}}{{Languages/Report bug}}		{{PageLang\|en}}{{Languages/Report bug}}
	{{Important\|		{{TNT\|Important\|
	* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs.		* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs.
	* 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.}}		* 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 '''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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu\|Main menu\|Help\|Report bug}}.		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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu\|Main menu\|Help\|Report bug}}.

Line 9:		Line 10:

	== Before reporting a bug ==		== Before reporting a bug ==

	* Update to the latest {{GlossLink\|development version}} (see [[Installation and update#Updating Miranda NG\|Updating Miranda NG]]).		* Update to the latest {{GlossLink\|development version}} (see [[Installation and update#Updating Miranda NG\|Updating Miranda NG]]).
	* Check if the problem persists (it may happen that it has been fixed).		* Check if the problem persists (it may happen that it has been fixed).
Line 14:		Line 16:

	== Effective bug reporting ==		== Effective bug reporting ==

	[[File:Reporting bugs 01.png\|200px\|thumb\|Screen 1]]		[[File:Reporting bugs 01.png\|200px\|thumb\|Screen 1]]

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

Line 30:		Line 34:

	=== How to attach files ===		=== How to attach files ===

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

	== I know when it got broken ==		== 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.		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)		* you can either compile the revisions yourself (that requires more knowledge and time)
Line 41:		Line 47:

	== After reporting an issue ==		== After reporting an issue ==

	* Monitor the issues you report.		* Monitor the issues you report.
	* Provide feedback and additional information if requested.		* Provide feedback and additional information if requested.

← Older revision		Revision as of 03:37, 7 August 2017
Line 2:		Line 2:
	{{Important\|		{{Important\|
	* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs.		* Please, make bug reports to our [https://github.com/miranda-ng/miranda-ng/issues tracker], so they won't get lost on forums or chatroom logs.
	* If you are unsure about the problem or want to bring more attention to it, you can mention it on [~~http~~://forum.miranda-ng.org our forum] or [xmpp:miranda-ng-int@conference.jabber.ru?join chatroom] too.}}		* 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 '''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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu\|Main menu\|Help\|Report bug}}.		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. Our bug tracker: https://github.com/miranda-ng/miranda-ng/issues You can easily access it using Miranda: {{Menu\|Main menu\|Help\|Report bug}}.

Reporting bugs - Revision history

Goraf: add language independent anchor for 'Effective bug reporting'

Goraf: fix categorization

Goraf: Marked this version for translation

Goraf: remove old langabar

Goraf: use localized links; add sort key for category; remove deprecated in HTML5 ; use semantically correct emphasis

Goraf: split translation unit

Goraf: add translate tags and variables

Goraf: Remove outdated parts

Goraf: Prepare for translation

Dart Raiden at 00:37, 7 August 2017

Goraf: use localized links; add sort key for category; remove deprecated in HTML5 `; use semantically correct emphasis`