Revision history [back]

In a customized Git strategy, versioning can be achieved through the implementation of a branching and tagging system. The basic idea is to create branches for different versions of the code and use tags to mark specific points in the development process.

Here are the steps:

1. Create a development branch for ongoing work and testing.
2. Create a production branch for stable releases that are ready for deployment.
3. Use feature branches to develop and test new features separately from the main development branch.
4. When a feature is ready, merge the feature branch into the development branch.
5. When the development branch is stable and ready for release, merge it into the production branch.
6. Create a version tag for the production branch at each release point.
7. Use semantic versioning (such as MAJOR.MINOR.PATCH) for version numbering to clearly communicate the extent and nature of changes made in each version.

Using this method, developers can easily keep track of different versions, maintain a stable production branch, and identify the scope and kind of changes made in each release.