On 2020-03-31 09:52:36 +0800 (+0800), 何义鹏 wrote: [...]
how should I use the semMem-ver tag? [...]
The way the OpenStack release managers do it is, as soon as a new stable branch is created from a release candidate tag on the master branch, they propose a change like this to master: https://review.opendev.org/685258 Note the "Sem-Ver: feature" in the footer of the commit message, that hints PBR to assume the next tag will at least increase the "minor" (second) part of the version number. If you want to hint at a coming increase for the "major" (first) part of the version number next you would instead put "Sem-Ver: api-break" there. You can find a brief description of this functionality in PBR's documentation: https://docs.openstack.org/pbr/latest/user/features.html#version There's also a lot more underlying detail in the spec from when that capability was first being added: https://specs.openstack.org/openstack/oslo-specs/specs/juno/pbr-semver.html Hopefully this helps. -- Jeremy Stanley