Managing-Releases.md

 ---
 title: Managing Releases
 ---
+
 # Overview
 There are many ways to manage software releases with Git.  Git does not require any particular method to denote a release, though the most common method is a Git tag, and this is recommended.  Further, Git Dev Platforms often provide a platform specific release feature as well.  Git does not require any particular versioning scheme, but Semantic Versioning is a popular choice and recommended.  The contents of release notes is also subjective, although at a minimum a Git diff between previous release tag and new release tag is recommended.
 
 # Denoting Releases
-Generally a Git tag should be used to mark a new release.  There are alternatives however as it's possible that a Git Branch could be used instead of a tag to mark a release, though this is less common and only useful in certain workflows - especially since a branch can always be created from a tag at a later time.  It's also possible to create a new separate repo on each release, though this is inefficient - many older software workflows that did not use version control systems such as Git relied on a new directory per release strategy so it's mentioned here for completeness.
+Generally a Git tag should be used to mark a new release.  There are alternatives however as it's possible that a Git Branch could be used instead of a tag to mark a release, though this is less common and only useful in certain workflows - especially since a branch can always be created from a tag at a later time.  It's also possible to create a new separate repo on each release, though this is inefficient - many older software workflows that did not use version control systems relied on a new directory per release strategy so it's mentioned here for completeness.
 
 Developer Platforms such as GitLab and GitHub provide a `releases` feature, that associate a Git tag with a release. This is recommended, as it allows easy association of release notes and release artifacts.