Have you seen or maintain code where developers added their names to identify the sections of code they changed and explanations of why those changes were made? With RTCi source control, you do not need to! As you make changes and deliver them to the RTCi repository, it tracks what sections of the code are changed, by whom and why.
The figure below shows the ruler section of the LPEX editor with different color codes for the different sections of code differentiated by time of change. When you hover your mouse over a particular section of the ruler, a popup will come up with information about author, time of change, comments and any associated work items. The same support is available in the Java editor, and editors for other file types.
RTCi Team Blog
5 Posts tagged with the rtci tag
When I first started using the Pending Changes view I was noticing that components I didn't have loaded and components that didn't have any changes were shown and cluttering up the view. There are two settings from the drop down menu of the view: Show components which are not loaded and Show unchanged components that you can use to change this behavior.
The next artifact I kept noticing in the view was my changes showing up under an unresolved node. I was always connected when doing my work, so I wanted to bypass the whole notion of having to do a check-in. If I could have all my changes automatically checked-in when I was connected that would simply things. Like before this is just another preference.
Window -> Preferences -> Team -> Jazz Source Control -> Check-in Policies
Preference: "Auto check-in local changes"
This cleaned up my Pending Changes view and I don't have to do the additional step of check-in, usually, except on those occasions when I'm not connected (for example, if I'm working while flying!)
There are some additional preferences that you can change to fit your own needs on the Changes Preference Page ( Window -> Preferences -> Team -> Jazz Source Control -> Changes ).
