Reporting bugs

I love the fact that there are so many ZDT users out there helping out and finding bugs. Still, there are many times where I get a bug report that doesn’t have enough information to be able to debug the problem. Here are a few guidelines that will help me out quite a bit.

1. Always include the ZDT log files. Starting with the recent 0.7.0rc2 release, there is now a ‘Report Bug’ option in the Help menu. Whenever, you encounter a problem, invoke this command and a zip file will be created with the log files I need. Just attach this file to any emails you send.
2. Include a clear description of the problem including the actions you were performing before the problem occurred. If you can reproduce the bug with a consistent set of steps, please include that information as well.
3. If applicable, screenshots are also very useful.

Just following these simple steps will make my life easier, and hopefully result in a more stable ZDT.

Add comment September 25th, 2007

0.7.0 rc1 test build available

I’ve just put up a 0.7.0 build up in the ZDT sandbox area on Sourceforge for people to play with. Keep in mind that this is not an official release. If you decide to download it, please leave me some feedback.

UPDATE 9/21: I found a nasty bug in the self review test, so I’m re-uploading a new build.

Add comment September 20th, 2007

ZDT Facebook group

If anyone has a Facebook account, come join the ZDT Facebook Group. Why? I don’t know. Just another medium to harass me with.

In other news, my goal is to have a 0.7.0 final release build ready for private testing sometime this week.  If you check out this wiki page, you’ll be able to see the features/bugs fixed as I complete them.

1 comment September 9th, 2007