On Fri, Mar 09, 2018 at 06:48:56PM +0100, Mathieu Bridon wrote: > On Fri, 2018-03-09 at 10:38 +0100, Pierre-Yves Chibon wrote: > > On Fri, Mar 09, 2018 at 10:12:37AM +0100, Mathieu Bridon wrote: > > > We could take a hint from how we make software upstream these days: > > > > > > 1. submit a pull request for the package in src.fp.o on the master > > > branch > > > 2. a CI automatically builds this package in Koji > > > 3. merge the pull request into master > > > 4. the build (from step 2) is tagged for Rawhide, without a rebuild > > > > > > Gating is achieved by preventing merges if the build/tests fail. > > > > This has been discussed but requires a way for koji to "promote" > > scratch builds > > to real builds and this isn't a small task. > > Long term, I do think this is a good idea anyway yes. > > It doesn't have to be scratch builds, it could be real builds in a side > tag. That would register in koji's DB the unique NEVRA which means, the PR can't be updated without bumping the release field. Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
