What is a useful Branch Versioning Strategy?

Question

We have moved to a product versioning approach which will mark/increment builds according to the following format: [Major].[Minor].[Build].[Revision/Patch], and a p

Answer 1

I wouldn't tie a version number to a feature branch, because in a concurrent development scenario, you might need to consider :

• only part of a feature (not everything might be ready for release within a feature)
• several feature (if one depends on another), meaning you would need to release several features as part of a new version.
• minor or major versions: not every stable point will increment just the build, a feature might introduce minor or major changes

For each new x.y release,Iwould rather have a dedicated branch for consolidation, where I can merge all the feature branches selected for the next release (since some features might not be ready in time),and where the x.ypart would make sense.

In other words, I would separate the feature development cycle from the release cycle.