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