From AbiWiki

---

Bugzilla: Bug Closed--Believed Fixed

Due to the large number of users compared to the number of developers, we sometimes close Bugs as FIXED even if we were not able to reproduce the problem before, or maybe test if the problem was actually fixed.

We do this because we have reason to belive the problem has been fixed due to changes to code that is likely responsible for the reported problem. Or if we could see how the problem was made possible by the code, but were unable to reproduce it ourselves for one reason or another (i.e. we tried fixing it in blind - we need you to check it out).

This should be considered a polite (if somewhat terse!) request for you to test if the problem has indeed been fixed in the latest version of . There are two very good reason for us to do this:

• You reported the problem, so you know how to reproduce it and check for sure if it has been fixed. This is a crucial point, especially for Bugs that may depend on things particular to your computer, or the tune you hum while you use .
• We save time - time we can spend on the next Bug.

When we ask you to retest, there may not have been a public release since the fix was made. If at all possible, we would like you to try one of the nightly built versions of . Please see the latest issue of AbiWordWeeklyNews for links to locations of nightly built images. Alternatively, make a note in the Bug that you will wait for the next release before you check if the problem has been fixed - then we all know that you have not given up on the Bug but are simply waiting for a binary, which is quite allright.

See also the [[[FaqBugPolicy|FaqBugPolicy]] Bug Policy].

-- Main.JesperSkov - 12 Jun 2002