Inconsistent release tag names

[terrytangyuan]

I found this when debugging kubeflow/mpi-operator#169. The most recent release https://github.com/kubernetes-sigs/kube-batch/releases/tag/0.5.0 should be named v0.5.0 instead of 0.5.0 to be consistent with previous releases.
cc: @k82cn

[k82cn]

oh, good catch! Let me correct that :)

[terrytangyuan]

Perhaps keep 0.5.0 and then just create another tag v0.5.0 from the same commit just in case anyone is already using the existing 0.5.0 tag.

[terrytangyuan]

@k82cn Any update on this? Could you create a new tag v0.5.0? I believe the existing tag is having issue with many dependency management systems - they cannot detect this correctly.

[k82cn]

ok, I'll update it today :)

[k82cn]

done :) xref https://github.com/kubernetes-sigs/kube-batch/tree/v0.5.0

[terrytangyuan]

Thanks!