Ok, here is an idea. At least post on Totalservice what ER codes are available, what they are supposed to fix. This way we know the option exists. Another plus would be "fill out this form before downloading the code". Then you all could spam our mailboxes and ask us to evaluate the code........a little automation, good for us, good for you, you don't have to pay those expensive tech support people just to hand us the ER code, you get your data, and we get our code. Brian On Tue, 12 Oct 1999, Todd Keister wrote:
Jeff:
I think you have missed the point. We don't just want to "Throw Code" at given issues. It may seem like extra steps, and sometimes it is laborious to follow these procedures, but in business, law, and especially in science, if you don't have clearly documented data trails, and reproducible results - then you have not accomplished a darn thing.
Once again: >This is done so that we can document the use of these special codes to >see if the code fixes the specific issue it was designed to address, AND also >to see if the new fix for one issue causes issues with any other >processes in the code or product.
If we were to just release code "willy nilly" and not track what we've done, it would be of no use to anyone, and we would be breaking many more things than we fix.
ER code is "special issue" code that addresses one speicific problem, and it is not feasible to stress check this code for all possible issues in all possible configurations. A specific ER code may have a known issue with another process - and that will be fixed before an ER is promoted to a Service Release. In the meanwhile customers who desperately need one item fixed, and who can "make due" while any other errors are resolved - can do just that - they can get the fix that they need - and they can get it NOW (which is the whole point of this process).
I hope this clarifies my prior statements, and I hope this helps to clarify what could on the surface seem to be another "Stupid Policy" that is actually just a part of the Scientific Method.
Todd ;-}
Jeff Mcadams <jeffm@iglou.com> on 10/12/99 12:12:31 PM
Please respond to usr-tc@lists.xmission.com
Sent by: Jeff Mcadams <jeffm@iglou.com>
To: usr-tc@lists.xmission.com cc: (Todd Keister/MW/US/3Com) Subject: Re: (usr-tc) 2.0.60 HDM Code
Thus spake Todd Keister
ER or Engineering Release Code is only available by calling to Tech Support, and then WE (Tech Support) must get permission to release the code.
Good grief, its getting worse. What's next? Are we going to have to get a note from our mother's to use ER code? Blech.
This is done so that we can document the use of these special codes to see if the fix the specific issue they are supposed address, and also to see if the new fix for one issue causes issues with any other processes in the code or product.
Is it at all possible that 3Com could ever *eliminate* beaurocracy in their processes rather than constantly adding layer upon layer of it?
I hope this helps.
Unfortunately, no, I doubt it really does. :/
Does anyone in upper management at 3Com listen to what we're saying? I sometimes get the distinct impression that they really don't give a crap what we feel. I guess that is progress though...we do have *some* people at 3Com listening to us now...even if they aren't the people making decisions on most of these things.
Jeff "getting frustrated with 3Com idiocy again" McAdams
- 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.
- 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.
----------------------------------------------------- Brian Feeny (BF304) signal@shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - 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.