Packager submits build using fedpkg (spec file uses %autorel and/or %autochangelog) Koji buildSRPMFromSCM step: rpmautospec_plugin (TBD: rename from rpmautospec_plugin as we have two plugins now DONE in PR#28): Detects presence of %autorel/%autochangelog in the spec file Release bumping code: Retrieves latest EVRs of the package for all Fedora versions (i.e. values of the %dist tag) from the Koji list of builds If needed, tags these latest builds in dist-git Pagure (TBD (Issues (#42) #43 #44 DONE in PRs #80, #97)

Small reminder: We aim for a Proof Of Concept/Prototype It will be opt-in We don't aim for 100% of the use-cases/packages We have 4 weeks left to work on this (deadline: end of March) Approach #1: <#commits>.<#builds>%{?dist} Use the number of commits since last version bump, and the number of builds for the same commit for the same Fedora version, and append %{?dist}.

Notes: We haven't yet decided definitively on the macro and option names. This document assumes Fedora 31 as the version a package should be built for. Normal release flow The most common case is release numbers which just get incremented for each build. For these, one could put the following into your spec file, to be filled in automatically: Release: %automatic_release