Hi! I feel a strong need to write about bug reporting, because some last posts are making my work harder. Here are the rules: Rule #1: -------- If you find a bug, search the archive, if it is not already reported. If so, you may provide some additional information (by replying, do not remove the content of the previous mail). Mails like "the same for me" are useless for me. Rule #2: -------- So, you have found a new bug. Then send a NEW e-mail. DO NOT REPLY to any e-mails from the list. Also, do not reply to my anouncement e-mails, if you are reporting a bug. It only creates chaos in the archive and in my mailbox too. And then it is harder for me to search the mails for bugs and then fixing them. Rule #3: -------- Each bug in a separate mail, please. Do NOT write one mail with a list of found bug. It is harder for me to process it. Rule #4: -------- Fill in the subject field with brief description of the problem. Rule #5: -------- Describe how to reproduce the problem. Some problems are hard to reproduce, then describe conditions and steps that lead to the problem. If it is related to a feed, send the URL of the feed. Without it I'm not able to reproduce it and therefore I'm not able to fix the problem. It you are reporting a crash, attach logfile. Logging feature is disabled by default, you can enable it by setting: HKCU\Software\DaProfik\pRSSreader, LogLevel[DWORD] = 5, LogFile[String]=<path\logfile> Compress long logfiles (zip is ok). Rule #6: -------- Please, write in English. Rule #7: -------- If I'm not responding that does not mean that I'm ignoring you. Maybe I'm busy with other work (do you remember, I'm making pRSSreader in my free time) or I'm working on your problem. If I need more info, I will ask. I will report the fixes, either directly in the archive as the reply to your email or in the anouncement email in the ChangeLog. If you are not sure what I ment with the previous paragraphs, take a look at Joerg's recent posts. Mails that do not follow these rules are automaticaly low-priority emails. I will deal with them later. Further reading on bug reporting is on http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Please read it. Do not take anything as an offense. It is a way for better cooperation and helps me to fix problems faster, thus it should lead to better pRSSreader. Thanks for your attention, -- David -- pRSSreader development mailing list prssr-devel-ml@xxxxxxxxxxxxx //www.freelists.org/archives/prssr-devel-ml