Git Tagging a New Version

Here is my way of generating version numbers of an application:

  • The version number convention is:
    • Major – a major version represents fundamental changes to the application, important feature(s) etc.
    • Minor – a minor update means new feature extensions (e.g. adding new visual effects to an app) or new permission requests
    • Patch – usually this is necessary for bug fixes or cosmetic changes (read: no new functionality to be added)

    This means that a version could be 0.4.0, no “v” in front.

  • Once the version is established, create the git tag:

  • and commit it:

Mind you that currently, the build script will show something like 0.4.0 - <commit key> if you do further commits after the tag is created.

PS: I wrote this because it’s not something I do often and I end up looking online on how to tag and commit stuff…

A little experiment: If you find this post and ad below useful, please check the ad out :-)

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to top