What you are referring to is a management issue, not a technical one. As VP-IT I required any emergency move to be accompanied by an explanation why the move took place, and what was corrected. When there was an unusual number of them, we had a reason for a chat, first with the Director of Development, then with the developers. Solved the problem quick.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 9/18/2012 3:04 PM, rob@xxxxxxxxx wrote:
The problem I have with "emergency" bypasses is that everyone considers
their situation an emergency. But maybe our levels are simple. If you
had a level where you couldn't promote to production until the controller
approved the test results then I can see an "emergency" bypass. In our
shop the same person can check out an item, promote from development to
test and then promote it from test to production. And it's fast enough,
and the emergency factor had better be rare enough, that it takes the
developer more time to remember how to use the emergency bypass than it
takes to just run it through the cycle.

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page