CODEWITHSUNDEEP
mercurialbranchrelease
T'n'E
T'n'E

Reputation: 616

Branching strategy for special releases

Later this week we are doing some tests on an embedded device. For this, we want to know exactly what software was tested, but we also have to make some modifications to it for testing purposes. The current strategy we use is based on the popular "A successful Git branching model". What we want is

We are leaning towards an unnamed branch with a tag at its head as it keeps the named branches to releases and features, but is still easy to find visually.

What would be the drawbacks of this approach and what other approaches are suitable?

Upvotes: 0

Views: 61

Answers (1)

planetmaker
planetmaker

Reputation: 6044

The drawback is similar to what a named branch offers: it's a permanent marker (though you can re-tag, thus move a tag).

However the better alternative is in this case to use a bookmark as that's by design a transient name which can be added or (re)moved to any revision you like at any time.

Upvotes: 1

Related Questions