Thus spake Steve Valiunas
The poor horse isn't even flinching anymore, but... We only perform limited in-house testing on ERs so they can go out quickly-( we don't run them through our internal testing group) so we try to be careful about their distribution. When I make an ER available I want to have accurate contact info for the customer so I can get ahold of them if something nasty shows up with it at a customer site. If after a number of days several users have indicated that it has fixed their issue and it warrants posting, it will become a candidate for being made available on totalservice for download as a ServiceRelease.
This would seem to be a contradiction of what most of us call BETA testing. If you only release ER code to a few select site.. then how can you verify your code base will work when put out for general consumption? Having two/three beta sites is not a through test.. it's more like an attempt to beta test. I would say release ER to all, then when customers call support (or an engineer) about problems with the ER they can talk to the person involved with the code... not a tech-bot in front of some database without a clue. Most people will not just install an ER unless they know they need it. If they do and it blows up.. then hey, it's a beta and you get what you get. 3Com's attempt to protect us from ourselves is not going over well. BTW.. what about a LINUX port of TCM!!!!!!!! Who can I mailbomb concerning this? Paul Farber Farber Technology farber@admin.f-tech.net Ph 570-628-5303 Fax 570-628-5545 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.