baseline usage for branching
In the projects, we want to create some versions containing one more changeset for branching that is major or minor versions. After deploying process, we think create some baselines to tag the versions. Could we pull that versions when prod environment has a problem or needs to create hotfix?
I check the link. https://jazz.net/forum/questions/48906/concept-of-branching-in-rational-team-concert. According to this link, creating a new branch equals to create a new stream in rtc. In some projects, there will be a lot of stream in this way and it will be complicated. Baseline usage is meaningful for branching?
Does creating baseline use much space in database or does it only mark a tag? I mean creating many baselines cause performance issues or not? We want to use brach approach in RTC? Thank you
Accepted answer
Eray,
please check out the article on Patterns of Stream Usage especially the links on multistream development. Baselines (or for that matter snapshots) are "cheap" objects, meaning they link rather than copy and can be created without much overhead or performance issues.
- Arne