12 ms·
> if your program doesn't work on their test environment Bold of you to assume they have one of those! Personally I assume they will break production, then cal
by 7steps2much 3y ago
> if your program doesn't work on their test environment
Bold of you to assume they have one of those! Personally I assume they will break production, then call you names because of it.
- jeroenhd 3y agoI realize that's a realistic problem. How you deal with people like that really depends on your environment. For open source software: too bad. The AS IS part of the license should cover expectations well. For commercial software: depends on the contract, really. If the contract hasn't specified anything, an upgrade document will work fine in many cases. For enterprise software: your customers won't update your software anyway. I'd go with warnings just to be safe. Maybe do it in three stages, first warnings, then severe warnings, then errors. If you really want to grab attention for your warnings, prefix them with <<COMPLIANCY RISK ALERT>> and you'll be sure to get them to read the upgrade guide!