From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "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: Tue, 20 Mar 2018 13:26:18 +0200 [thread overview]
Message-ID: <61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LadpoW1BCCbfhsEac7PBV2qNxuiWrnRk6MZeV2DVWiDEA@mail.gmail.com>
On 03/20/2018 12:52 PM, Burton, Ross 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.
Alex
next prev parent reply other threads:[~2018-03-20 11:32 UTC|newest]
Thread overview: 13+ 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 ` akuster808
2018-03-19 20:07 ` Burton, Ross
2018-03-20 10:07 ` [yocto] " Alexander Kanavin
2018-03-20 10:52 ` Burton, Ross
2018-03-20 11:26 ` Alexander Kanavin [this message]
2018-03-20 15:59 ` Richard Purdie
2018-03-20 18:00 ` Alexander Kanavin
2018-03-20 21:08 ` Tim Orling
2018-03-21 22:54 ` Richard Purdie
2018-03-21 14:24 ` Philip Balister
2018-03-21 14:31 ` Alexander Kanavin
2018-03-21 14:40 ` 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=61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox