If it's not in Bugzilla, it doesn't exist.

FreeDOS Bugzilla We have moved from Bugzilla 2 to a Bugzilla 3 on a new server. This finally allows our Bugzilla to send emails again. Bug numbers stay the same and old bookmarked URLs redirect to the new server now. Thanks to Markus Maussner for the hosting and all the installation help!

Click the link below to enter Bugzilla:

Do not report problems with the FreeDOS Bugzilla to the staff at SourceForge - they cannot help you. If you get software errors when using Bugzilla, please contact the webmasters to report the problem.

Bugzilla is a database for bugs. It lets people report bugs and assigns these bugs to the appropriate developers. Developers can use Bugzilla to keep a to-do list as well as to prioritize, schedule and track dependencies.

The methodology that seems to work best for tracking FreeDOS projects in Bugzilla is documented below:

  • The tester enters a bug in Bugzilla. The bug is automatically assigned to the default component owner (usually the project owner.)
  • The component owner reassigns the bug to the most appropriate developer. At this point, the bug is still in NEW status.
  • The developer accepts the bug, and starts work on it. The bug is now marked ASSIGNED.
  • The developer provides a fix for the bug, and checks the new code into CVS. Once the code has been checked in, the bug is marked as FIXED.
  • If everything looks okay to the tester, the bug is marked VERIFIED. But if the tester finds the bug has not been fixed, the bug becomes REOPENED, and it goes back to the developer. (Please speak with the project owner before moving a bug to REOPENED.) Note that the bug has not changed hands, and is still assigned to the developer, since he was the last person to write code for it.
  • When the build has been released "officially", the project owner then marks all the fixed bugs for that milestone as CLOSED.