As a user of automatic release bumping, I want that the flags of the %autorelease macro are working, so that I can use it for snapshots and pre-releases and the like.
%autorelease
<extraver>
<snapinfo>
Structure of the release field covering complex versioning cases: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_more_complex_versioning
The hotfix flag in the prototype isn't necessary because we don't plan to guarantee a clean upgrade path anymore, i.e. where a package in Fedora version N - 1 would always sort "earlier" as in Fedora version N. Actually, we can't do this without the historical build information the prototype stored in git tags, and we don't have to because upgrades are done with the equivalent of dnf distro-sync, i.e. "upgrade or downgrade to the (epoch-)version-release found in the repo". The purpose of this flag was to turn off the "wiggle-room" for a release number in the normal case which was necessary to allow builds for several Fedora versions from the same commit, i.e. when they had no knowledge that the other builds happening at the same time would e.g. bump the release in Rawhide—therefore we let the build for one Fedora version bump the release to a value one higher than what was found in newer Fedora releases. The flag would have been used when changing things in older Fedora version without a flanking change in a higher Fedora version, to then use the <minorbump> field instead.
dnf distro-sync
<minorbump>
Metadata Update from @nphilipp: - Issue set to the milestone: Production Ready - Issue tagged with: F35 Change, Release Bumping Algorithm Functionality
Metadata Update from @nphilipp: - Issue marked as depending on: #143
Metadata Update from @amoloney: - Issue assigned to dkirwan
Commit 64d1b7f fixes this issue
Metadata Update from @nphilipp: - Issue unmarked as depending on: #143
Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.