Re: Frustration and more frustration trying to install a V11 desktop app on another P
This is obviously a frequently overlooked and under-utilized "band-aid" to the problem. This being said, how is one to know "which and what update breaks what?" (Since there is no way for the general user base to gain insight as to exactly what problems are created with each particular update!) Also, due to the complexity of a5, I suspect many users (developers / end users too) encounter "broken code" long after it was actually broken by an update..... So it can also be difficult to know exactly which version you need to rollback to! (And rolling back can cause problems with new databases failing too.)
IMHO, the smart solution (short of not releasing new code that breaks old code) would be to have a user supported bug submission (and search) system in place, instead of sending bugs in by email.....
If implemented properly:
I think this would solve a lot of PR issues, increase user confidence, while making it much easier for Alpha to both classify & respond to the important issues. (And, without all the individual email correspondence, I think it would make it a lot easier on Alpha's administrative side of things too!) If you really think about it, the entire update cycle (presently in use by Alpha) without any user accessible bug tracking knowledge-base whatsoever makes for a really poor combination......
Actually..... Why doesn't Alpha just build their own custom web bug service with A5?
(A couple of weeks and they could have something of their own up and running!)
The company (Alpha) is "great."
The program (a5) is "fun."
The forum is "invaluable."
The wiki is "usable."
The wishlist is "questionable."
...But the whole update & bug tracking process is "lacking." *
*Although I do know that Selwyn & customer service work very diligently to provide the best support possible given the current methods in place!
Originally posted by Selwyn Rabins
View Post
IMHO, the smart solution (short of not releasing new code that breaks old code) would be to have a user supported bug submission (and search) system in place, instead of sending bugs in by email.....
If implemented properly:
- Users could search for existing issues, versions, resolutions, workarounds etc....
- We could classify, submit (with examples) and rate bug severity directly to a "bug tracker" service.
(instead of sending an email to one recipient) - Alpha could then validate/confirm the reported bugs, and add support/versioning/fix info.
- This would create a quick perspective of bug importance via frequency of submissions too!
I think this would solve a lot of PR issues, increase user confidence, while making it much easier for Alpha to both classify & respond to the important issues. (And, without all the individual email correspondence, I think it would make it a lot easier on Alpha's administrative side of things too!) If you really think about it, the entire update cycle (presently in use by Alpha) without any user accessible bug tracking knowledge-base whatsoever makes for a really poor combination......
Here's a huge list of them, some of which are even free...... (Pick one that "fits" and run with it!):
http://en.wikipedia.org/wiki/Compari...em_integration
http://en.wikipedia.org/wiki/Compari...em_integration
Actually..... Why doesn't Alpha just build their own custom web bug service with A5?
(A couple of weeks and they could have something of their own up and running!)
The company (Alpha) is "great."
The program (a5) is "fun."
The forum is "invaluable."
The wiki is "usable."
The wishlist is "questionable."
...But the whole update & bug tracking process is "lacking." *
*Although I do know that Selwyn & customer service work very diligently to provide the best support possible given the current methods in place!
Comment