bob_new_version.py misses a good "default" for version numbers
Created by: anjos
This is a very useful script. It would be an awesome addition if we could have either a flag (or the absence of any) to implement a "default" version releasing.
How would that work?
- bob_new_version.py reads the file
version.txt
and figures out what is the "next" release. - It sets the stable version to that value (minus the
aX
,bX
orrcX
complements, of course). - It sets the latest version to be the value in item 2 above + one minor patch number. For example, if the value on
version.txt
was '2.0.5b0', thenstable = 2.0.5
andlatest = 2.0.6b0
.
This way it would be possible to issue something like:
$ ./bin/bob_new_version.py --default-release
And get the ball rolling. This would also allow us to batch release a number of packages at once, w/o taking into consideration differences between release numbers.
If a new API release is on the horizon, the developer must updated "version.txt" so that the file version.txt
is correctly preset (e.g., to 2.1.0b0
). This way bob_new_version.py --default-release
will do the right thing next time.
@siebenkopf: What do you think?