Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

A picture is worth a thousand words. What does the Source Control model look like?

0
Posted

A picture is worth a thousand words. What does the Source Control model look like?

0

The above diagram is an overview of how Source Control artifacts relate to each other. We use dotted lines to represent the Repository Workspace and the Stream. The resources represented by these two objects typically vary in time. On the other hand, the Snapshot is in some ways like a frozen state of a Repository Workspace or Stream. As such, it is represented with a bold line. • Components, baselines and change sets can flow between a Repository Workspace and a Stream through Accept, Deliver, Replace with, Replace in • A Repository Workspace is typically loaded into a Sandbox. An Eclipse Workspace acts as the default Sandbox • Resources in a sandbox can be created, edited or refactored through the client IDE or other native editors. • Resources added, modified, renamed or deleted can then be stored in (or removed from) a Repository Workspace by doing a check-in into a Change Set that belongs to a particular Component in the Repository Workspace. Eclipse projects or other top folders

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123