When should TAG be used compared to BRANCHING and vice versa (in CVS)?

I think the name should be good enough.

+5
source share
4 answers

Tags

Think of it as a snapshot. I want to be able to return to this point. However, it will never change. You do not check on the marked item.

Things that can be marked:

  • Releases (major and minor)
  • Patches sent to customers
  • Bugs fixed.
  • Milestones (alpha, beta, etc.)
  • Successful daily build

Branches

(, ).
(, ).
, .
( ).

, , .

+3

, . , .

, /.

+5

, . .

0

,

We use tags for small release releases and release branches. For example,

v1.0 <-- Branch  
  v1.0.1 <-- Tag  
  v1.0.2 <-- Tag  
v1.1 <-- Branch  
  v1.1.1 <-- Tag  
  v1.1.2 <-- Tag  
v1.2 <-- Branch  
  v1.2.1 <-- Tag  
  v1.2.2 <-- Tag  
v1.3 <-- Branch  
  v1.3.1 <-- Tag  
  v1.3.2 <-- Tag  
v1.4 <-- Branch  
  v1.4.1 <-- Tag  
  v1.4.2 <-- Tag  
v1.5 <-- Branch  
  v1.5.1 <-- Tag  
  v1.5.2 <-- Tag  

To use the Microsoft analogy, Branch is the Windows edition (95, XP, Vista, etc.), and the tag is the service pack.

0
source

All Articles