Bump version number to x.[y+1]-dev after tagging/publishing a release

[sun]

Problem

• The version number in git remains to be the last released one, even though it may contain further changes already.

Goal

• Ensure development snapshots can be properly identified.

Proposed solution

1. Parse current version numbers from files.
2. Ask user to enter new version number (with automated suggestion).
3. Change the version number (using sed).
4. Do the review/commit/tag/release shebang.
5. Ask user to enter new dev snapshot version number (with automated suggestion).
6. Change and commit the new dev version number to git.

[netsensei]

Okay. Sounds good. I've annotated the flow to make it more clear:

1. Parse current version numbers from files
2. Ask user to enter new version number (ie skip a number) (with automated suggestion: x.y)
3. Change the version number in the files (using sed).
4. Do the review/commit/release shebang (includes creating a git tag x.y)
5. Ask user to enter new dev snapshot version number (with automated suggestion: x.[y+1]-dev)
6. Change to the new dev snapshot version number in the files again (using sed).
7. Commit the updated files to the master branch in git.