Re: Batched updates for development cycles

[Randy Barlow]

I filed an issue to request this change:

https://github.com/fedora-infra/bodhi/issues/1895



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Peter Robinson]

On Sat, Oct 14, 2017 at 11:14 PM, Randy Barlow
 wrote:
> 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.

Daily run by cron job, only composes that are special events are
release candidates.

>>> 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 ☺

;-)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Randy Barlow]

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 ☺



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Peter Robinson]

On Sat, Oct 14, 2017 at 5:11 PM, Randy Barlow
 wrote:
> On 10/12/2017 03:06 AM, Peter Robinson wrote:
>> It seems batched updates is turned on for F-27 [1], surely it makes
>> sense for updates to go straight out in the development cycle, this
>> affects things getting into the nightly composes for testing in live
>> images and other such things.
>>
>> I feel this should be something that is only used for stable releases.
>
> Hey Peter!
>
> 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.

> 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.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Randy Barlow]

On 10/12/2017 03:06 AM, Peter Robinson wrote:
> It seems batched updates is turned on for F-27 [1], surely it makes
> sense for updates to go straight out in the development cycle, this
> affects things getting into the nightly composes for testing in live
> images and other such things.
> 
> I feel this should be something that is only used for stable releases.

Hey Peter!

Since branched releases have the updates-testing repository enabled by
default, won't the effect you desire happen anyway?

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.



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Matthew Miller]

On Thu, Oct 12, 2017 at 07:12:51AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > It seems batched updates is turned on for F-27 [1], surely it makes
> > sense for updates to go straight out in the development cycle, this
> > affects things getting into the nightly composes for testing in live
> > images and other such things.
> > 
> > I feel this should be something that is only used for stable releases.
> > 
> > [1] https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609
> ... or we could make the batches go out daily to still test the
> batching mechanism as far as possible without actually delaying
> anything.

Ooh, that's a good idea. +1.


-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Peter Robinson]

On Thu, Oct 12, 2017 at 8:12 AM, Zbigniew Jędrzejewski-Szmek
 wrote:
> On Thu, Oct 12, 2017 at 08:06:18AM +0100, Peter Robinson wrote:
>> Hi All,
>>
>> It seems batched updates is turned on for F-27 [1], surely it makes
>> sense for updates to go straight out in the development cycle, this
>> affects things getting into the nightly composes for testing in live
>> images and other such things.
>>
>> I feel this should be something that is only used for stable releases.
>>
>> [1] https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609
>
> ... or we could make the batches go out daily to still test the
> batching mechanism as far as possible without actually delaying
> anything.

Sure, I don't care what the implementation details are.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Batched updates for development cycles

[Zbigniew Jędrzejewski-Szmek]

On Thu, Oct 12, 2017 at 08:06:18AM +0100, Peter Robinson wrote:
> Hi All,
> 
> It seems batched updates is turned on for F-27 [1], surely it makes
> sense for updates to go straight out in the development cycle, this
> affects things getting into the nightly composes for testing in live
> images and other such things.
> 
> I feel this should be something that is only used for stable releases.
> 
> [1] https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609

... or we could make the batches go out daily to still test the
batching mechanism as far as possible without actually delaying
anything.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org