Update Preversioning explanation to avoid double that

While there's nothing wrong with a double that, when reading this
section I found that it was a bit distracting and made the section
harder to parse than necessary.

Change-Id: I9ca982a8ad6b3a6fd5c4a8b42b93ad2540b2f1ee
This commit is contained in:
Sachi King 2016-04-14 13:06:31 +10:00
parent d4e29cb5d2
commit dcc49c54f5
1 changed files with 4 additions and 4 deletions

View File

@ -58,10 +58,10 @@ major version increment.
If postversioning is in use, we use the resulting version number as the target
version.
If preversioning is in use - that is, if there is a version set in
`setup.cfg` metadata - then we check that that version is higher than
the target version we inferred above. If it is not, we raise an error,
otherwise we use the version from `setup.cfg` as the target.
If preversioning is in use we check that the version set in the metadata
section of `setup.cfg` is greater than the version we infer using the above
method. If the inferred version is greater than the preversioning value we
raise an error, otherwise we use the version from `setup.cfg` as the target.
We then generate dev version strings based on the commits since the last
release and include the current git sha to disambiguate multiple dev versions