inconsistent release titles on GitHub and irrelevant message for tags #74

See release titles on left side of this page:
v0.4.4
Release v0.4.3
Release v0.4.2
Release v0.4.1
release version 0.4.0
v0.4.0 release candidate 1
v0.3.1
version 0.2.3
Version 0.2.2
Version 0.2.1

Please rename to be consistent (naming scheme doesn't matter as long as it is consistent).

Also, in most cases, the release tag messages displayed by git tag -n are not related to the tag :
v0.1 Release 0.1
v0.2.0 Merge pull request #49 from dave3d/RenameProject
v0.2.1 Merge pull request #50 from dave3d/FixVersionBug
v0.2.2 Merge pull request #52 from dave3d/MakeTestsPythonic
v0.2.3 Merge pull request #56 from dave3d/UpdateREADME
v0.3.0 Tweak dictionary
v0.3.1 Tweak dictionary
v0.4.0 Merge pull request #61 from SimpleITK/PythonBackend
v0.4.0-rc1 Merge pull request #61 from SimpleITK/PythonBackend
v0.4.1 version 0.4.1
v0.4.2 Merge pull request #64 from SimpleITK/AddCSharpType
v0.4.3 Merge pull request #68 from SimpleITK/UpdateREADME
v0.4.4 Merge pull request #70 from dave3d/DisableOption

In the future, tag the release locally with a command like:
git tag -a v0.4.5 -m "Release 0.4.5"

Then do a git push v0.4.5 upstream, assuming this repository is your local upstream and then create the release on GitHub.