BugClosedNotOurProblem
From AbiWiki
(Difference between revisions)
m (Reverted edits by Unotefuca (Talk) to last revision by Maintenance script) |
|||
Line 1: | Line 1: | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | === Bugzilla: Bug Closed& | + | === Bugzilla: Bug Closed—Not Our Problem
=== |
Some Bugs report problems in the use of which are not really in the realm of proper - i.e., in pieces of software that the developers do not have control over. A Bug closed referring to [[BugClosedNotOurProblem|BugClosedNotOurProblem]] should state where the problem is belived to originate from - the reporter can then try to get help from whoever developed that piece of software. | Some Bugs report problems in the use of which are not really in the realm of proper - i.e., in pieces of software that the developers do not have control over. A Bug closed referring to [[BugClosedNotOurProblem|BugClosedNotOurProblem]] should state where the problem is belived to originate from - the reporter can then try to get help from whoever developed that piece of software. |
Revision as of 13:18, 27 November 2010
Bugzilla: Bug Closed—Not Our Problem
Some Bugs report problems in the use of which are not really in the realm of proper - i.e., in pieces of software that the developers do not have control over. A Bug closed referring to BugClosedNotOurProblem should state where the problem is belived to originate from - the reporter can then try to get help from whoever developed that piece of software.
Examples could be (but are not limited to):
- Problems reported against plugins that are not from http://www.abisource.com
- Problems with underlying software components; developers should strive to feed such Bug reports upstream since the user is likely to notice only the symptom, whereas the developer would understand the cause of the problem.
See also the [[[FaqBugPolicy|FaqBugPolicy]] Bug Policy].
-- Main.JesperSkov - 13 Jun 2002