All issues (both defects and enhancements) can be filed in qooxdoo’s issue tracking system Bugzilla. Before reporting a bug, please search Bugzilla if such a bug has already been reported. This helps to keep the number of duplicate bug entries low.

• Typical bug reports (i.e. obvious defects) should be entered straight into Bugzilla. Please do not post such bug reports to the mailing list. This keeps the mailing list from being cluttered and also allows for a dedicated bug handling.

• Take special care in assigning the proper attributes, e.g. qooxdoo component, browser, operating system, etc.

• There are two attributes that are particularly important to setup and maintain a proper workflow for addressing and fixing the issue: severity and priority. Please do not change these values from their default values, i.e. keep the initial values severity normal and priority P3. Those attributes are adjusted during bug triage by the framework maintainers.

• If you found an existing bug report you are interested in, you may add a comment with some additional information and/or put yourself on CC, so that you are informed by email about all changes to the bug report.

There are two types of issues, defects and enhancements.

• Defects are typically planned to be fixed in the next release. If it is not possible in the corresponding time frame, bugs may be moved to a milestone after the next release. All defects should have an assignee.
• All other bugs are regarded enhancements, independently of requireing small or large changes. The priority setting is used to order these bugs for the next planned milestone. Only enhancements which are actually planned to be released in a reasonable time frame should be assigned. Unassigned enhancements are a “pool” of additional features, which contributors are welcome to address.

When you have successfully resolved a bug or you want to propose an enhancement, you can contribute your code changes as a so-called “patch file“. This text file contains the differences between your local version and the SVN version. The patch file can easily be included with the bug report as an attachment.

In order to create a patch you need to have checked out the original SVN trunk version of qooxdoo, to which you made your changes locally. You can then either use the diff command-line tool, or the convenient functionality your IDE provides. In Eclipse you can simply select folders or files, then choose Team / Create Patch... from the context menu and follow the wizard to save a patch file to your file system.

Besides attaching patches to a bug report you can also add a screenshot. Often such a screenshot helps in understanding what the actual problem is. Please make sure the screenshot file is only as large as necessary, so you might want to crop the original image.

As an alternative to Bugzilla’s regular web frontend there are several alternative tools available:

You may use Deskzilla, for which an open-source community license for the host qooxdoo.org has been granted.

Another very powerful tool that helps working in a task-oriented way is the Mylyn plugin for Eclipse IDE.

• Target 0.8.3

• Target 0.7.x (all open bugs)

• Target 0.7.x (open “major” and “critical” bugs only)

• Target 0.9

• Target unspecified (all open bugs)

• Real bug reports, but no target or old target specified

• Reported by Eclipse RAP (excluding enhancements)

• Reported by Eclipse RAP (excluding enhancements, excluding 0.8 targets)

• Reported by Eclipse RAP (excluding enhancements, targeted for 0.8.x)

• New bugs from the last seven days sorted by importance
• New bugs from the last seven days sorted by creation

• All new bugs sorted by priority
• All new bugs sorted by creation date

• Fixed bugs of the last seven days sorted by last change