SQL Power Software Forum

This message was edited 3 times. Last update was at 2009-05-11 13:03:24

This is copied over from the Power*Architect Bugs forum, but I figured this would be worth re-posting for Power*MatchMaker users.

If you think you've found a bug in the Power*MatchMaker, here is our recommended course of action.

First, try to reproduce the bug in the latest build. Every time we change the MatchMaker source code, our continuous build server produces a new downloadable version of the MatchMaker. The most recent successful build is always available at http://trillian.sqlpower.ca/hudson/job/power-matchmaker/lastSuccessfulBuild/.

If you can successfully reproduce the bug in the latest build, please check out the Google Code Issues database (http://code.google.com/p/power-matchmaker/issues/list) and see if the bug has already been reported.

Older issues may also be found in our Bugzilla database at http://trillian.sqlpower.ca/bugzilla. You can use the 'Search existing bug reports' feature to look for the bug you found.

If a bug report already exists, you can add a comment to the bug describing any additional information that may be missing. You can also click on 'Vote for this bug' to indicate to the development team that you would like to see this bug fixed.

If no bug report exists, then you can contribute a bug report into the Issues database (http://code.google.com/p/power-matchmaker/issues/list), as well as notifying the development team via this Support Forum.

We strongly recommend that you include in your report:

1. A step-by-step description of how to reproduce the bug.
2. What outcome you were expecting to see, especially for User Interface glitches.
3. The version of DQguru (or Power*MatchMaker if you're running an older pre-0.9.5 version), Java Runtime Environment, and OS that you were running.

Quality bug reports are extremely valuable for improving the Power*MatchMaker, so we greatly appreciate them!

Sincerely,
The Power*MatchMaker Team