On Sat, 26 Jan 2013 05:49:25 +0000 (UTC)
Ben Boeckel <mathstuf@xxxxxxxxx> wrote:
> 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.
Seems complex. Would it run on the client or on the server side?
It also seems... unexpected. You ask for a build, but it does commits
and builds behind your back?
> 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?
That would need some kind of queue...
kevin
Attachment:
signature.asc
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
