How about an "official bug" section?
As you probably know, Progress Software doesn't list most of the known bugs of the latest OpenEdge version.
I sometimes waste a couple of hours (...days) on something, make a call to Progress tech support just to know from them that my problem is due to a bug they already know about.
From my calls to tech support, I also get a new "official" bug number for new bugs that they didn't knew about (including documentation bugs ("doc bugs") i.e. something in the documentation that is wrong or too incomplete... this too causes to loose precious time sometimes).
How about having a new Hive section where everybody could share their bugs with the official bug number, the Progress product and version it's in and when it's stated to be corrected (when Progress gives that info) with any details and workaround?
- Login to post comments
Bugs in the Knowledge Center
Would progress putting the bugs into the knowledge center help out at all?
That would be the best
Of course! That would be the best!
You code, tumble on something strange, search the KC, find what you are looking for, stop loosing time.
My biggest problem is that when I find a bug, before I open a Tech Support call, I have to isolate the bug / make it easily reproducible (and that's the long part) because that will be the first question the support person asks: "how can we reproduce it".
Because we are always using the latest OE version, I'd say that I tumble on 1/3 existing bugs and 2/3 new bugs.
I was lazy the other day and opened a call just to know if it was already a documented bug, but it's a bit silly that I have to ask someone at Progress to search their bugs database when I could do it myself and save the trouble.
Feel free!
I can think of a couple of ways that any Hive user could accomplish this. The most sensible, probably, would be to create a new "project" node, and use the issue tracking features of the project node in order to build up a database of the bugs you want to track.
Complicated
The complicated piece is that the bugs are tied to specific versions and sometimes even specific service packs, so one would almost have to tie each entry to the individual version and pack number ... and then one has the problem of identifying that a particular bug is fixed in a particular version or service pack while another is not.