Rational Team Concert is good for task and requirements tracking as we use it, but klunky for source management. I've tested the SCM component and you have to set up i projects with RDP and check out ALL members.
Even using SVN directly with RDP requires that you use i projects. Yie !!
My current strategy is to catch a source member change when it is opened for editing and archive the original and changed source deltas with SVN automatically each day so the day to day stuff can be managed pretty much the same as always, but all source gets captured automatically.
Vern I mastered capturing the sequence and date info so that won't get lost and can be used in SEU and RDP that way.
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Fri, 18 Jan 2013 09:08:31 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: Retrieve Source change informatio
Makes sense - probably a good solution is something that uses an SCM
that stores deltas - like SVN - and Rational Team Concert can work with
SVN repositories - ba-da-bing!
Of course, not cheap! Unless you are a vendor.
On 1/18/2013 8:59 AM, Jon Paris wrote:
On 2013-01-18, at 8:57 AM, midrange-l-request@xxxxxxxxxxxx wrote:
Thanks all....Can anyone help with journaling the source file changes? Not that adept at journaling...We studied it recently and it was of no use to us.
The individual records are not updated. What appears to happen is that a working copy of the file is made and that is what the editor operates on. The entire member is then deleted and re-added. Consequently what appears in the journals is of limited value if you are trying to check who changed what as you only see member level actions.