Search code examples
rtc

In RTC source control should streams be deleted

Given RTC streams are the 'branch' equivalent should you allow them to be deleted after they are no longer actively used (preserving any snapshots by moving them to another stream)?

My current thinking is yes they can be - to keep the work area tidy-er. So if one product has several streams e.g. I may do:

Stream DevEng [delete]
Stream IntEng [delete]
Stream FixEng [delete]
Stream RelEng [Keep]

Since the only thing you lose is the ability to query the stream to see if it every saw a particular component baseleine.

Are there other negatives? What policy do you have?

Solution

  • The other alternative is to rename and reuse.
    But deleting is a viable option.

    In any case, that means the baselines and snapshots are not tightly linked to a Stream (which can be renamed or deleted at any time).
    As a result, it is important to adequately name said baselines and snapshots in order to remember their purpose.