On Thu, 24 Jan, 2013 at 02:41:50 GMT, Kevin Fenzi wrote:
> % bodhi -L systemd
> f16-updates systemd-37-25.fc16
> f16-updates-candidate systemd-37-25.fc16
> f16-updates-testing systemd-37-25.fc16
> f17-updates-candidate systemd-44-22.fc17
> f17-updates-testing systemd-44-23.fc17
> f17-updates systemd-44-23.fc17
> f18-updates-testing systemd-195-15.fc18
> f18-updates systemd-197-1.fc18.1
> f18-updates-candidate systemd-195-14.fc18
Looking at this, how about a simple rule about what makes a fedpkg build
cascade up: While the next higher branch has the same version, but older
pre-dist release number, merge --ff-only and trigger a build if one is
not created within an hour of the current build completing. With this, a
bump in the form %{?dist}.1 wouldn't trigger a build (since this implies
that it's a release-specific fix) and a build on fX won't trigger an
fX+1 build if there's a version gap between them.
Sending an email halfway between the end of the build and automation of
intent would probably be useful. If the next higher branch is updated
manually and no build appears, this could be interpreted as a "I know
what I'm doing" indication and cancel the automation.
Thoughts?
--Ben
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
