|
In most of our project site, we do not normally allow developers to delete anything/source other than development, this is normally managed thru a Change Management Software. However, there were occasions we need control the changes manually, on the box or different, a little source authority control can do the trick most of the time. Different connection might not solve our problem sometimes; especially when I need to work on a few projects concurrently and there could be enhancement on certain area that has dependencies across projects. Thanks & regards, Leonard Thum thumls@xxxxxxxxxxxxxxx -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Samuel J Lennon Sent: Friday, May 26, 2006 5:14 AM To: wdsci-l@xxxxxxxxxxxx Subject: Re: [WDSCI-L] Enhancement Request I wondered about this too. My developer id can't delete production objects, and I'm very greatful for that. When developement and production were on the same box we carefully segregated production and development using OS/400 authority, and we still do that even with a separate development box. And for larger companies, this is probably a SOX requirement. Sam >From: <Rick.Chevalier@xxxxxxxxxxxxxxx> >Reply-To: Websphere Development Studio Client for >iSeries<wdsci-l@xxxxxxxxxxxx> >To: <wdsci-l@xxxxxxxxxxxx> >Subject: Re: [WDSCI-L] Enhancement Request >Date: Thu, 25 May 2006 13:13:17 -0500 > > >I'll probably regret this but... > >Why do you have production code and development code in the same filter? I >presume that's the case. Here, our production code is on a separate system >so it's not much of an issue. If it was contained on the same system >though, I'd want to separate it somehow. Maybe even a separate connection >that just contained production or development libraries. > >Then again, maybe all that is being done and I'm just naïve in thinking you >would be safe with the code in separate connections or filters. > >Rick *** Privileged/Confidential Information may be contained in this message. *** If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message, and notify us immediately.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.