Surgient Success

Does Surgient post a public known bug list?  it would be helpful.  I keep running into quite a few bugs and it would be nice to know if they are known or not so i can document and forward them to surgient.

The product Release Notes contains a Known Issues section, this is as of that particular release.  Each subsequent release contains the list of known issues for that release.

Like other software companies our internal bug list isn't published publically.  If you have issues, please post them here or contact Surgient support.

Sorry if this appears argumentative, but I guess it is meant to be.

Too often consumers (end-users) bear the burden of having to deal with known issues.  Too often these are identified through first hand experience.  These persons then call the support line which may or may not be aware of the issue which then triggers a call to 2nd or 3rd tier support.  Why not join efforts to help stop this madness by simply publishing the confirmed issues?  I think it would be considered very proactive and improve customer-vendor relations and save a whole ton (or tonne if you are of the persuasion) of time and effort.  (Just my 2 cents)

Sincerely, HiEdTechie

It would be a really great idea to publish the confirmed issues and also their possible solutions, so that there would be one common repository where you can verify the issues encountered are known issues. This should save a lot of time for a user.

Sincerely,

Praveen. 

One of the items was we planned for but were unable to provide online initially is a Knowledge Base.  Obviously we have and generate a lot of information internally and grooming that data for useful, accurate public consumption is a daunting task.  We do have all of this knowledge captured but not necessarily in one place. :)

We are aware that timely information about known issues and a general knowledge base is a need and something we are not currently providing.  By asking as you have for this information, just validates the need is out there.

Hopefully as progress is made, we will be able to make an announcement about the availability of a Knowledge Base where information about resolved issues in between releases is addressed.

NOTE: That our Service Packs do include more frequent ReadMe information about resolved issues in between releases.  The next step would be to provide a vehicle for confirming issues that we're working on addressing in future Service Packs.

As an end user, I can see why people would want and expect a list of known bugs in a software product.  Afterall, it just makes complete sense that you wouldn't want to hit a known bug, fight yourself figuring out why, what caused it, how to get around it, am I the only one seeing this kind of things...

On the other hand, working in the software industry, you also don't want to put every known bug out there.  From my experience, most bugs that are easily identified get fixed.  The bugs that usually get through are obviously the ones QA didn't catch, the one's that 90% will never see, the one's that aren't easily reproduced and therefore hard to fix because the developer may either think they fixed it or never sees it again.

It's a fine line, and both sides of the fence have their reasons for wanting and not wanting it displayed for all to see.  A knowledge base is a great idea as well, as it should cover at least immediate bug identifications so that people can find it, send it in, get it fixed or identified with a workaround or something.