0

Can you please explain them using concepts of Git?

Also, is there any situations when operations on outgoing set could be dangerous?

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
Henry
  • 2,819
  • 3
  • 18
  • 33

2 Answers2

2

RTC (Rational Team Concert from IBM) is a centralized VCS (Version Control System).
As opposed to Git, which is decentralized.
So any direct comparison between the two will be limited and fraught with inaccuracies.

But the closest Git notion you could have from:

  • an outgoing change set (one that you could deliver from your repo workspace to your RTC steam) would be Git staged files (set of files ready to be committed to your current branch,
  • an ingoing change set (one that has been published to an RTC stream and is ready to be accepted into your repo workspace) would be what is ready to be merged after a fetch: git diff --name-only origin/master

As for a delicate operation on change set, one example would be "Reversing change sets", which can remove the changes captured in a change set and create a patch.
See more at "Managing change sets in RTC": discard and suspend can also have an impact on (espacially outgoing) change sets.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Despite the limitations you outline regaring decentralization vs centralization, I think this is a fair comparison. +1 4 QnA –  Jan 13 '19 at 17:54
1

I'll add that an outgoing change set cannot be delivered on a source member, if the same source member has an incoming change set. You must accept/merge the change set in before you can deliver the outgoing change set.

Other than that, the only other real "danger" is delivering code to a stream when you've not tested your code (i.e. unit tested) locally.

Kenny
  • 316
  • 1
  • 9