'git flow hotfix start' and 'git flow release start' will suggest
a new version number based on previous tags in the respository.
The respective stop commands will suggest the same version number.
Version numbers are in the form [major].[minor].[revision]
(eg. 1.3.5). 'hotfix' assumes a revision bump and 'release' assumes
a minor bump, but suggestion can be overridden. In addition
'git flow hotfix start 1.0.0' and 'git flow release start 1.0.0'
still work as expected.
Tag sort is now done by date on the tag, not alpha. This should
ensure we're always looking at the latest tag when incrementing
version number while remaining much simpler than a version sort.
Tags that are created by feature finish and hotfix finish are now
auto-annotated with the version number. This can still be
overridden by adding a -m flag with message to the finish call,
but avoids an unnecessary interruption since the actual tag
message is mostly worthless, but we have to have it to get
author and date metadata.
Previous versions attempted to guess version number on finish
based on version number auto-incrementation. It's more intuitive
to guess based on current branch on finish as that honors a user
override of default version number incrementation on release or