All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	"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 22:54:56 +0000	[thread overview]
Message-ID: <1521672896.25754.226.camel@linuxfoundation.org> (raw)
In-Reply-To: <a73785d4-f3fb-374d-3a54-3ea97e85b41f@linux.intel.com>

On Tue, 2018-03-20 at 20:00 +0200, Alexander Kanavin wrote:
> On 03/20/2018 05:59 PM, Richard Purdie wrote:
> > 
> > > 
> > > > 
> > > > 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.
> > Personally I'm leaning to every couple of weeks...
> My worry is that shorter AUH periods will lead to reminder fatigue.
> Also the period between submitting the updates, and having them show
> up in master is sometimes less than ideal, even when the freeze is
> not in effect.

Its a valid concern? Once every three weeks? I would like to make
things more available for people if possible too...

With builds we've had a bad run at the moment and am hoping with
improvements in build resources that are in process we can fix that.

Cheers,

Richard


WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	"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 22:54:56 +0000	[thread overview]
Message-ID: <1521672896.25754.226.camel@linuxfoundation.org> (raw)
In-Reply-To: <a73785d4-f3fb-374d-3a54-3ea97e85b41f@linux.intel.com>

On Tue, 2018-03-20 at 20:00 +0200, Alexander Kanavin wrote:
> On 03/20/2018 05:59 PM, Richard Purdie wrote:
> > 
> > > 
> > > > 
> > > > 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.
> > Personally I'm leaning to every couple of weeks...
> My worry is that shorter AUH periods will lead to reminder fatigue.
> Also the period between submitting the updates, and having them show
> up in master is sometimes less than ideal, even when the freeze is
> not in effect.

Its a valid concern? Once every three weeks? I would like to make
things more available for people if possible too...

With builds we've had a bad run at the moment and am hoping with
improvements in build resources that are in process we can fix that.

Cheers,

Richard


  parent reply	other threads:[~2018-03-21 22:55 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               ` Richard Purdie [this message]
2018-03-21 22:54                 ` Richard Purdie
2018-03-21 14:24           ` [OE-core] " Philip Balister
2018-03-21 14:24             ` [yocto] " Philip Balister
2018-03-21 14:31             ` [OE-core] " Alexander Kanavin
2018-03-21 14:31               ` [yocto] " 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=1521672896.25754.226.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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 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.