Monthly seems like a good enough cadence to give everyone time to review
the mails, send the mails, get reviewed on the list, go through the
autobuilder, and eventually reach master.  Too fast and AUH will be sending
nagging mails for a patch which is shortly being merged.

Can we stop bikeshedding now? :)

Ross

On 21 March 2018 at 14:31, Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> On 03/21/2018 04:24 PM, Philip Balister wrote:
>
>>      Which brings me to a question: what is a good schedule and cadence
>>>>      for AUH runs? Currently it's run on the 15th of every odd-numbered
>>>>      month (so January, March, and so on), but I thought of shifting it
>>>>      one month forward, so it doesn't land right in the middle of a
>>>>      feature freeze. Thoughts?
>>>>
>>>>
>>>> How long does a single run take, and why not run it every month?
>>>>
>>>
>>> Just a bit longer than a day, maybe 30 hours, if it needs to update the
>>> typical amount of 100-150 packages. I'll shift it to monthly then.
>>>
>>
>> Maybe bi-weekly? Could that help reduce the number of upgrades needed
>> for each run?
>>
>
> Only if the maintainers take those reminders as high priority items, and
> actually send out the patches quickly, and then those patches make it to
> master. All that needs to happen within those two weeks. Otherwise, the AUH
> will just re-run the same set.
>
> Alex
>