Hi Reg

Talking about problems rather than bugs is a practical matter for me, not based on an attempt to be polite. Problems include bugs. To call a problem a bug requires the user to know what was in the mind of the developer when creating the software. This is not always obvious.

Although Composer users with a background in software development might be interested to have some insight into the project development and programming of Composer, I do not think that it is a good idea to publish a database of bug reports with redundancies removed or any such list, beyond what is already available from reading postings on the forum.

It is important that a user reports his or her experience, not influenced by an official list. The frequency of reports on a particular problem is an important guide for setting priorities.

Clyde makes some good additional points.


Best wishes,

Herbert