accept 1.0 version number for set-release task

The `set-release` task didn't work with 1.0 version numbers. This PR fixes the misbehavior.
Okay, I got it wrong. Should we change our buildnumber to comply to the form a.b.c+number instead of a.b.c-number?