On 10/14/2017 12:45 PM, Peter Robinson wrote: >> Since branched releases have the updates-testing repository enabled by >> default, won't the effect you desire happen anyway? > No, because the updates-testing repo is enabled by default for > installs, it's not enabled for the composes so things like Live, ARM > and cloud images when composed don't include the contents of > updates-testing. If you updated them once they are booted they pull in > testing, but the pungi compose that generates them only consumes the > f27 tag. Ah, that makes sense. Do composes happen every day for branched, or are they special events? I ask because the way Bodhi moves updates from batched to stable is by running a very simple CLI (via cron). If the composes are special non-daily events, maybe releng could simply run that script when they want to make a compose. If they are daily events, I think we'll need to patch Bodhi so that it skips the batched thing for branched releases. >> I'm not opposed to modifying the system so that it doesn't batch for >> stable releases, but I'm curious why the default updates-testing repo >> doesn't satisfy the need. > You're confusing stable releases (F25 and F26) vs development/branched > releases (F27) and see above for the answer to that. IMO the stable > releases should have batched updates, the branched releases either > shouldn't or if they do the 'batches' should be sent out daily. Sorry, I meant to say "branched" instead of "stable", and actually that second paragraph was redundant with my first one and I could have just left it off ☺
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
