git flow release start fails when using -v / --verbose option

[ChrisJStone]

When attempting to start a new release with -v or --verbose command fails with following output:

flags:WARN getopt: unrecognized option '--verbose'
 -- '0.0.0' ''
flags:FATAL unable to parse provided options with getopt.

Should support be added for a verbose option? If so what should be listed?

[ChrisJStone]

The underlying cause of this bug has been resolved and pushed to develop. I'm keeping this issue open for now. Once a decision has been reached on if verbose output should be added to release start this will be updated accordingly.