I am not sure I totally agree with this premise. This forum seems to be split between the occasional poster, who is simply looking for help with problems they encounter, versus the active members who see it as a community. (Considering, I got up this morning and decided to check what the guys on HE where discussing, puts me into the later category, LOL).
I am sure there are many HE owners that have never visited this forum, and many others who visit very rarely and simply post when they have an issue. By nature all these posts are going to start with phrases similar to: "Error when ....", "There is a Bug with this ....", "This is not working as it should...."
I do see your point with the phrase "There is a bug", to me it seems a little presumptuous, just because the software is not acting as one expects, does not mean it is not acting as intended. Some (although not the majority) of posts I have read in the past that mention a bug, sound a little too much like: "This is not exactly how I want the software to work, therefore it is a bug, and I am reporting it..."
As a recent example, I came across a problem creating a rule. I first checked the "known issues" list for the release I was on and it did not appear to be one of the listed issues (often the list of known issues, does not detail the problems you may encounter with the issue, so it can be difficult to know if the problem you are encountering is a "known issue"). I created a thread with the title "Error when trying to create ....", described my problem and Bruce quickly replied: "
There are some problems with this action in 2.3.3.134. Working on them now...."
It was fixed in the next release (2 days later) and all is well. Was this a bug? Could I have titled my thread "There is a bug..." I don't know, I don't really understand the word "bug", I feel its better to just accurately describe what you are experiencing, rather then assuming something is wrong with the software. (Thread I am referencing: Error when trying to create a rule)
