All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	akuster808 <akuster808@gmail.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: Tue, 20 Mar 2018 12:07:32 +0200	[thread overview]
Message-ID: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbxDGNrJH8tDiCgMKoSHUsK8Q17BUH=UVkY8zDBAm70+g@mail.gmail.com>

On 03/19/2018 10:07 PM, Burton, Ross wrote:
>     Do we have a place identified for new changes (2.6) while 2.5
>     stabilizes.
> 
> 
> A formal place, no.  I tend to queue stuff in a branch if master isn't 
> taking all of my energy, otherwise the patches will sit on the list 
> until 2.5 releases.  Typically master and sumo branches won't diverge 
> until post-release.

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?

Alex


WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	akuster808 <akuster808@gmail.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 12:07:32 +0200	[thread overview]
Message-ID: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbxDGNrJH8tDiCgMKoSHUsK8Q17BUH=UVkY8zDBAm70+g@mail.gmail.com>

On 03/19/2018 10:07 PM, Burton, Ross wrote:
>     Do we have a place identified for new changes (2.6) while 2.5
>     stabilizes.
> 
> 
> A formal place, no.  I tend to queue stuff in a branch if master isn't 
> taking all of my energy, otherwise the patches will sit on the list 
> until 2.5 releases.  Typically master and sumo branches won't diverge 
> until post-release.

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?

Alex


  reply	other threads:[~2018-03-20 10:14 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     ` Alexander Kanavin [this message]
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             ` [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=833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=akuster808@gmail.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.