lbry-sdk/.bumpversion.cfg

[bumpversion]
current_version = 0.13.1rc1
commit = True
tag = True
parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)((?P<release>[a-z]+)(?P<candidate>\d+))?
serialize = 
	{major}.{minor}.{patch}{release}{candidate}
	{major}.{minor}.{patch}

[bumpversion:part:candidate]
first_value = 1

[bumpversion:part:release]
optional_value = production
values = 
	rc
	production

[bumpversion:file:lbrynet/__init__.py]
add bumpversion script 2016-07-05 20:25:36 +02:00			`[bumpversion]`
Bump version: 0.13.0rc1 → 0.13.1rc1 2017-06-14 21:55:57 +02:00			`current_version = 0.13.1rc1`
add bumpversion script 2016-07-05 20:25:36 +02:00			`commit = True`
			`tag = True`
Normalize python version setuptools will force a version to be 'normalized' which means that it removes the dash. This will probably cause some weirdness on the version numbers in the windows build; might have to re-work my patches on cx_freeze: https://bitbucket.org/jobevers/cx_freeze/commits/all 2016-11-11 21:34:01 +01:00			`parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)((?P<release>[a-z]+)(?P<candidate>\d+))?`
Bump version: 0.9.0 → 0.9.1rc1 2017-03-15 17:34:32 +01:00			`serialize =`
Normalize python version setuptools will force a version to be 'normalized' which means that it removes the dash. This will probably cause some weirdness on the version numbers in the windows build; might have to re-work my patches on cx_freeze: https://bitbucket.org/jobevers/cx_freeze/commits/all 2016-11-11 21:34:01 +01:00			`{major}.{minor}.{patch}{release}{candidate}`
Add release candidates to bumpversion The release process now looks like: starting version: 0.7.5 bumpversion patch -> 0.7.6-rc0 bumpversion candidate -> 0.7.6-rc1 bumpversion release -> 0.7.6 2016-11-11 14:19:39 +01:00			`{major}.{minor}.{patch}`
add bumpversion script 2016-07-05 20:25:36 +02:00
no more rc0 2017-03-15 17:32:49 +01:00			`[bumpversion:part:candidate]`
			`first_value = 1`

Add release candidates to bumpversion The release process now looks like: starting version: 0.7.5 bumpversion patch -> 0.7.6-rc0 bumpversion candidate -> 0.7.6-rc1 bumpversion release -> 0.7.6 2016-11-11 14:19:39 +01:00			`[bumpversion:part:release]`
			`optional_value = production`
Bump version: 0.9.0 → 0.9.1rc1 2017-03-15 17:34:32 +01:00			`values =`
Add release candidates to bumpversion The release process now looks like: starting version: 0.7.5 bumpversion patch -> 0.7.6-rc0 bumpversion candidate -> 0.7.6-rc1 bumpversion release -> 0.7.6 2016-11-11 14:19:39 +01:00			`rc`
			`production`
Bump version: 0.7.5 → 0.7.6-rc0 2016-11-11 19:04:21 +01:00
update version info 2017-02-21 01:21:49 +01:00			`[bumpversion:file:lbrynet/__init__.py]`
Bump version: 0.9.0rc8 → 0.9.0rc9 2017-02-22 19:51:10 +01:00