Reportingbugs - Revision history

Octalot: New section "Missing music or images", about partial installs

2021-08-26T20:44:33Z

New section "Missing music or images", about partial installs

Konrad2: /* Guidelines for suggesting features */ updating the must read link

2019-03-19T15:52:42Z

‎Guidelines for suggesting features: updating the must read link

Konrad2: /* Guidelines for suggesting features */

2019-03-19T15:52:14Z

‎Guidelines for suggesting features

Vultraz: Removed whole Bug Protocol section. It didn't really say anything.

2018-03-21T20:36:49Z

Removed whole Bug Protocol section. It didn't really say anything.

Vultraz: Removed outdated protocol entries.

2018-03-21T20:33:29Z

Removed outdated protocol entries.

Celtic Minstrel: /* Needed information */ Needs more labels!

2017-11-09T01:45:02Z

‎Needed information: Needs more labels!

SigurdFireDragon: /* Bug protocol */ Some updates for GitHub

2017-05-31T23:42:58Z

‎Bug protocol: Some updates for GitHub

Pentarctagon: /* Guidelines for suggesting features */

2017-05-27T14:33:52Z

‎Guidelines for suggesting features

Celtic Minstrel: Screenshots shouldn't be put in a zip

2017-05-06T19:46:27Z

Screenshots shouldn't be put in a zip

Pentarctagon: /* Guidelines for reporting bugs */

2017-05-06T05:01:29Z

‎Guidelines for reporting bugs

@@ Line 51: / Line 51: @@
 === In-play problems ===
 If it is in-play problem that you can reproduce, save the game and send the savegame to us with details how to reproduce the problem from the savegame.
 === Multiplayer out-of-sync errors ===

@@ Line 30: / Line 30: @@
 # First, please make sure the feature you are suggesting does not already exist (particularly in the latest development version of the game, consult the [http://changelog.wesnoth.org changelog]) by double-checking the help files and options to make sure you aren't missing something.
 # If it hasn't been implemented, please check that it hasn't been already submitted, by searching [http://bugs.wesnoth.org http://bugs.wesnoth.org].
-# If your feature request hasn't been submitted, start a topic about your feature at the [http://www.wesnoth.org/forum/ Forums] after reading [https://forums.wesnoth.org/viewtopic.php?f=12&t=34904 "MUST-READ About the Ideas Forum"].
+# If your feature request hasn't been submitted, start a topic about your feature at the [http://www.wesnoth.org/forum/ Forums] after reading [https://forums.wesnoth.org/viewtopic.php?f=12&t=34904#p505264 "MUST-READ About the Ideas Forum"].
 # If you get positive results on the forum (preferably from at least one developer) you can go ahead and submit your feature request using the [https://github.com/wesnoth/wesnoth/issues issues] tab on Github.
 # Please post only one feature per feature request. If you have multiple feature ideas that are related, you can cross reference them easily with "bug #123".

@@ Line 30: / Line 30: @@
 # First, please make sure the feature you are suggesting does not already exist (particularly in the latest development version of the game, consult the [http://changelog.wesnoth.org changelog]) by double-checking the help files and options to make sure you aren't missing something.
 # If it hasn't been implemented, please check that it hasn't been already submitted, by searching [http://bugs.wesnoth.org http://bugs.wesnoth.org].
-# If your feature request hasn't been submitted, start a topic about your feature at the [http://www.wesnoth.org/forum/ Forums] after reading [http://www.wesnoth.org/forum/viewtopic.php?t=10152 "Giving your idea the best chance of being accepted"].
+# If your feature request hasn't been submitted, start a topic about your feature at the [http://www.wesnoth.org/forum/ Forums] after reading [https://forums.wesnoth.org/viewtopic.php?f=12&t=34904 "MUST-READ About the Ideas Forum"].
 # If you get positive results on the forum (preferably from at least one developer) you can go ahead and submit your feature request using the [https://github.com/wesnoth/wesnoth/issues issues] tab on Github.
 # Please post only one feature per feature request. If you have multiple feature ideas that are related, you can cross reference them easily with "bug #123".

@@ Line 67: / Line 67: @@
 * You can attach files if you submit your bug through Github by dragging and dropping the file onto the comment box.
 * You can attach files to forum posts.
 [[Category:Troubleshooting and Bugs]]

@@ Line 70: / Line 70: @@
 == Bug protocol ==
 * A bug which has been fixed is closed immediately.
 * If a bug has been in a named release, add a milestone for the next release when it is fixed.
 [[Category:Troubleshooting and Bugs]]

@@ Line 14: / Line 14: @@
 * Can you reproduce the problem? If you can please provide steps to do it.
 On special request another note: Use common sense! If you know the information can't be relevant to your report simply omit it. Nevertheless too much information usually doesn't hurt.
 == How to be ignored ==

@@ Line 72: / Line 72: @@
 * We use the Status values "None" (awaiting action), "Fixed", "Won't Fix", "Invalid" (not a bug), "Works For Me" (unreproducible), or "Need Info".
 * A bug which is fixed is marked "Fixed" by a developer, probably the one committing the fix or reviewing it.
-* A bug present in a release is marked "Closed" only upon a new release containing the fix.
+* A bug which has been fixed is closed immediately.
-* Any bug present only in [[WesnothRepository]], and not in any named release, is marked "Closed" as soon as it is fixed.
+* If a bug has been in a named release, add a milestone for the next release when it is fixed.
 [[Category:Troubleshooting and Bugs]]

@@ Line 63: / Line 63: @@
 === Sending savegames, screenshots, coredumps, etc ===
-* Please compress the files (bzip2, gzip, zip).
+* Please compress the files (bzip2, gzip, zip). Do not compress images or sounds, unless you're posting several in a batch. In particular, don't compress screenshots.
 * You can attach files if you submit your bug through Github by dragging and dropping the file onto the comment box.
 * You can attach files to forum posts.

@@ Line 40: / Line 40: @@
 # If it hasn't been fixed yet, please check that the bug hasn't already been reported, by [http://bugs.wesnoth.org http://bugs.wesnoth.org].
 # If your bug hasn't been reported, please go ahead and report it.
-# Please post only one bug per bug report. If you have multiple bugs that are related, you can cross reference them easily with "bug #123". See the [https://gna.org/cookbook/?func=detailitem&item_id=236 Markup Reminder] for more details.
+# Please post only one bug per bug report. If you have multiple bugs that are related, you can cross reference them easily with "bug #1234", where 1234 is the number of the previous bug report.
 Keep bug reports to the point, and make sure your bug is easily reproducible given the information you provide.  Clearly written, reproducible single bug reports will get attention before those reports that mix several different bugs into one report, or that are incomprehensible.
@@ Line 46: / Line 46: @@
 If there is already an existing bug report, do not hesitate to add a comment with your details - this way we know when some bug is getting "popular".
-''Please login to Gna! before reporting bugs''
+An account at Github is free and takes very little time to set up.
 === In-play problems ===
@@ Line 66: / Line 64: @@
 === Sending savegames, screenshots, coredumps, etc ===
 * Please compress the files (bzip2, gzip, zip).
-* You can attach files if you submit your bug through Gna!, else
+* You can attach files if you submit your bug through Github by dragging and dropping the file onto the comment box.
 * You can attach files to forum posts.