As an example providing information on bugs, see Mike Bombich's forum page for Carbon Copy Cloner: <http://forums.bombich.com/viewforum.php? f=12&sid=f1fc006f711bb1c03a2502b875bd32ff>
Another program I use, PDFPen, has several workarounds listed in its FAQs for specific problems. I have seen similar "known issue" lists with other software. Apple does something vaguely similar (although more opaque) with articles on its support site. Closer to home, SpamSieve has a FAQ, blog archive, and a forum, as well as a /request/ soliciting comments on improving the software. <http://c-command.com/spamsieve/support> Noting bugs, known issues, and workarounds for users is not unprecedented. Regards, - Winston Mikael Byström wrote: >Winston Weinmann suggested: > >>That is a great idea, and one CTM should have both on its site and in a >>Read Me with the installer. >In a Readme? What other products put their buglists there? Isn't an URL >to some kind of online source sufficient? >After all buglists are not primarily around to warn people, but to focus >bug-*fixing*. > >I can imagine when an open bugfix list could be of use for the >developers of PowerMail, but as there isn't one in place I assume they >think otherwise or at least that the developers don't find it worth the >effort. > >I would think CTM do keep an inhouse buglist for internal use. > >Mikael > >Tech facts: >PM 5.5.3 Swedish | OS X 10.4.8 | Powerbook G4/400 Mhz | 1GB RAM | 80GB HD > > > >
