Yikes
So your method is "LIVE" testing.
How large a change are you allowed/willing to do?
What do you do if you have to introduce a new process that the system presently does not have?



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Wednesday, April 25, 2012 10:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: survey: frequency of in-house coded software enhancement promotions to production

Nathan replied to the list, and I don't mind sharing my responses, so I will do likewise.

On Wed, Apr 25, 2012 at 10:24 AM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:
How often does your shop promote in-house source code enhancements to
production?

This question almost doesn't make sense in our shop. "Promote"? We work directly with production software all the time.

Ages ago (long, long before I started) the company bought software (that I guess we would call an ERP today), including source code.
That software got customized beyond all recognition and is now essentially our company's own custom ERP. We have three RPG programmers, and all of us just compile directly to production at our discretion.

1)      Frequency of promotions into Production of home-grown software
enhancements (not break/fix patches & not vendor upgrades) - ie daily,
weekly, monthly, or anytime.

Any time. (And the word "promotion" doesn't even really apply.)

2)      Do you agree with the frequency?

Yes. For our shop and our software, it would not be cost-effective (and perhaps just plain not effective) to have more layers, more bureaucracy, and more formal processes.

3)      What problems do you see with the frequency?

It does depend on the three of us knowing what we're doing, and communicating with each other. (So it's not resistant to incompetent or unprofessional team members. But all of us have been here more than 10 years, and we haven't added anyone new in that time.)

John
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].