bugs

Reporting bugs and requesting new features

Should I send a bug report?

Yes Please!

With the 0.9.x version serie, we are polishing the code for the stable 0.10.x series.

So when Conglomerate crashes, then please file a report.

Similarly, if you've got an idea for how to improve Conglomerate, please get in touch!

Issues we know of

You can find a list of easy-to-fix bugs here, perfect for getting involved.

Program Bugs

Show all known coding bugs

Website Bugs

Show all known website bugs

Enhancement Requests

Other Bugs

How do I report bugs?

The conglomerate-devel mailing list
Bugs are tracked in GNOME's bugzilla database.
You can submit Conglomerate bugs and enhancement requests here .
Patches should be attached to existing bugzilla bugs rather than sent to the mailing list. When reporting a new bug you'll get a chance to attach a file to it immediately after opening the bug. Please use the PATCH keyword in bugzilla, and remember to patch the ChangeLog, too.

What information is needed for a bug report?

version numbers of Conglomerate, GTK+, GNOME, and other related software
description of the bug
information to reproduce the bug

stack dump, if relevant:

gdb src/conglomerate ; run ; *crash* ; where

keep it small but detailed
if possible, provide a patch

How do I create a patch?

Take code from cvs
Modify that version
Check it compiles
Edit the ChangeLog
Use cvs to build a patch
```
cvs diff -u > my_fix.patch 
```
Add the patch to bugzilla (see above).