David, I agree! This is my main argument for driving the sdlc / change control from within U2. ( And of course my product, PRC. )
Plus you can control all kinds of outside stuff - talking back and forth to other products - from within U2. Those other applications cannot 'drive' the change control for the rest of the things inside U2 besides basic programs in directories. Plus a separate solution for data integrity is still required. Susan Message: 13 Date: Fri, 4 Mar 2011 17:59:11 +1100 From: "Hona, David" <[email protected]> To: 'U2 Users List' <[email protected]> Subject: Re: [U2] Version Control Message-ID: <297b19fd90fdb14da1c8ceff0b6cffe76a3fee8...@vaunsw139.au.cbainet.com> Content-Type: text/plain; charset="us-ascii" If you are using U2 environment a lot of stuff won't work without utilising the VOC some fundamental or critical way. VOC entries for files, programs, paragraphs/PROCS, etc. Granted, in some cases these don't change often. Unless you are like some poor sites I have seen and run their entire or parts of their application process from a paragraph or proc in the VOC file - more common than you would like to think or hope! Likewise, control information inside U2 files are in many case extremely critical for many applications - this also needs to be managed and versioned, rolled-back if required, etc., etc. Any configuration management application needs to take everything into account not just source code. - _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
