Open main menu

Difference between revisions of "HOWTO-Admin"

1,623 bytes added ,  08:08, 26 November 2012
→‎How to triage bug reports: Further update to bug triage guide.
(→‎How to triage bug reports: Final draft of Bug Triage Guidelines.)
(→‎How to triage bug reports: Further update to bug triage guide.)
Line 53: Line 53:
*** Attached savegame for replication.
*** Attached savegame for replication.
** Any indication that the user has violated Rule #0? If so, then a comment should be posted referring them to [[Copyright_FAQ]] by URL.
** Any indication that the user has violated Rule #0? If so, then a comment should be posted referring them to [[Copyright_FAQ]] by URL.
** The admin should perform a search of the bug tracker, especially with respect to open bugs, to assess if the issue has previously been reported.
*** If the issue has been reported before, but has not been fixed, then a comment referring to the URL of the open bug should be attached, any useful information transferred to the original bug and the bug closed as "duplicate".
*** If it has been reported since the last stable release, but has been fixed in the development repository, then a comment referring to the URL of the fixed bug and indicating that the user should use a daily build or wait for the next release should be attached, prior to closure of the bug with conclusion "out-dated".
*** If the issue has been reported before, but the bug was previously fixed, then a comment referring to the URL of the bug should be attached as this may indicate a regression in the fix, or at least help indicate the cause.
*** Bugs pending information or confirmation of a fix by the user should be set "pending". Originally, the tracker automatically closed these after 14 days or so, unless a comment was added, but this function has been broken/disabled for some time, but they are often closed manually by an admin when it becomes clear they are  either lacking sufficient information to be progressed, or fixed/invalid and the user is unresponsive. This is partly why it is important to respond quickly to bugs with insufficient information to ensure that valid bugs are not closed spuriously as the user has got lost in the period of time between submission of the bug and when a developer gets time to look at it.
** If the bug is reporting "a crash", then the first possibility is to eliminate corrupted, missing or variant datafiles. The usual response to this is:
** If the bug is reporting "a crash", then the first possibility is to eliminate corrupted, missing or variant datafiles. The usual response to this is:
  This sounds like corrupted, missing or variant datafiles. Please can you try copying your datafiles   
  This sounds like corrupted, missing or variant datafiles. Please can you try copying your datafiles   
TrustedUser
574

edits