All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Philip Balister <philip@balister.org>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status WW12’18
Date: Wed, 21 Mar 2018 16:31:40 +0200	[thread overview]
Message-ID: <ccc3ea2f-f22a-930a-8912-489963dae8f4@linux.intel.com> (raw)
In-Reply-To: <b65227e0-d37f-6ae6-9f4c-4c535460143e@balister.org>

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


WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Philip Balister <philip@balister.org>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Yocto Project Status WW12’18
Date: Wed, 21 Mar 2018 16:31:40 +0200	[thread overview]
Message-ID: <ccc3ea2f-f22a-930a-8912-489963dae8f4@linux.intel.com> (raw)
In-Reply-To: <b65227e0-d37f-6ae6-9f4c-4c535460143e@balister.org>

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


  reply	other threads:[~2018-03-21 14:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 15:45 Yocto Project Status WW12’18 Jordan, Robin L
2018-03-19 19:22 ` [OE-core] " akuster808
2018-03-19 19:22   ` akuster808
2018-03-19 20:07   ` [OE-core] " Burton, Ross
2018-03-19 20:07     ` Burton, Ross
2018-03-20 10:07     ` [OE-core] " Alexander Kanavin
2018-03-20 10:07       ` [yocto] " Alexander Kanavin
2018-03-20 10:52       ` [OE-core] " Burton, Ross
2018-03-20 10:52         ` [yocto] " Burton, Ross
2018-03-20 11:26         ` [OE-core] " Alexander Kanavin
2018-03-20 11:26           ` [yocto] " Alexander Kanavin
2018-03-20 15:59           ` [OE-core] " Richard Purdie
2018-03-20 15:59             ` [yocto] " Richard Purdie
2018-03-20 18:00             ` [OE-core] " Alexander Kanavin
2018-03-20 18:00               ` [yocto] " Alexander Kanavin
2018-03-20 21:08               ` [OE-core] " Tim Orling
2018-03-20 21:08                 ` [yocto] " Tim Orling
2018-03-21 22:54               ` [OE-core] " Richard Purdie
2018-03-21 22:54                 ` [yocto] " Richard Purdie
2018-03-21 14:24           ` [OE-core] " Philip Balister
2018-03-21 14:24             ` [yocto] " Philip Balister
2018-03-21 14:31             ` Alexander Kanavin [this message]
2018-03-21 14:31               ` Alexander Kanavin
2018-03-21 14:40               ` [OE-core] " Burton, Ross
2018-03-21 14:40                 ` [yocto] " Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ccc3ea2f-f22a-930a-8912-489963dae8f4@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philip@balister.org \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.