Kevin Kofler wrote: > The idea would be that you'd be able to file and queue the update in Bodhi > as soon as the primary build completes, just as now, except that "primary" > would now be the one, possibly fake, architecture. The updates could even > get pushed right there, for the internal primary architecture only. So what it boils down to is that you wish you didn't have to wait for the build to complete in Koji before you submit the update in Bodhi, and you're proposing this big waste of build server resources as a way of reducing the wait a bit. Did you consider that the wait may actually become longer as the build servers will be much busier when they have to build both the real packages and the build-speed-optimized throwaway packages? If the Fedora community agrees that it would be good to be able to submit an update before the build has completed, then the right solution is to change the user interface of Bodhi to allow that. An even better solution might be a combined interface where you could start a set of builds and submit the update information as a single operation. Björn Persson
Attachment:
signature.asc
Description: This is a digitally signed message part.
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
