Updates to many products, including dvdfab, often include bugs. Major updates, often more bugs. You know this only too well. And you ask your customers, who have paid good money to help you test your products.
Yet you pleace those very same customers at risk of having their licences, and purchases of potentially several hundreds of dollars, blacklisted.
Signals, please don't bite my head off!
With all due respect, I think it would be good if you could find a way to support the people who use and test your products, with some form of indemnification against being blacklisted. A beta or temporary key, or an expiration date on the beta software... Something that allows concurrent use.
I have a test computer. I never install beta software on my production machine. But if I test on this machine I run the risk of losing my licence, even though all I'm doing is trying to help you guys and show you some support.
Good testing means not only testing new features, but comparing new against old. This means being able to run two versions concurrently, either on the same PC or different PCs (if the software can only be installed once on a machine due to technical limitations, not licence limitations).
It seems a bit harsh to say to people "it may contain bugs" and "can you pelase help us test and evaluate it" and then "if you do what we ask we may black list your licence".
I'm coming from 20 years experience as a programmer.
I mean no disrespect - even Micro$oft are not this tough on beta testers. And yes, I understand that Micro$oft products are less often updated and tested on a much bigger scale.
Yet you pleace those very same customers at risk of having their licences, and purchases of potentially several hundreds of dollars, blacklisted.
Signals, please don't bite my head off!
With all due respect, I think it would be good if you could find a way to support the people who use and test your products, with some form of indemnification against being blacklisted. A beta or temporary key, or an expiration date on the beta software... Something that allows concurrent use.
I have a test computer. I never install beta software on my production machine. But if I test on this machine I run the risk of losing my licence, even though all I'm doing is trying to help you guys and show you some support.
Good testing means not only testing new features, but comparing new against old. This means being able to run two versions concurrently, either on the same PC or different PCs (if the software can only be installed once on a machine due to technical limitations, not licence limitations).
It seems a bit harsh to say to people "it may contain bugs" and "can you pelase help us test and evaluate it" and then "if you do what we ask we may black list your licence".
I'm coming from 20 years experience as a programmer.
I mean no disrespect - even Micro$oft are not this tough on beta testers. And yes, I understand that Micro$oft products are less often updated and tested on a much bigger scale.
- Benjamin Franklin 1706-1790
Comment