From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>, Trevor Woerner <twoerner@gmail.com>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
Alexander Kanavin <alexander.kanavin@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] LAYERSERIES
Date: Fri, 06 Apr 2018 22:56:53 +0100 [thread overview]
Message-ID: <1523051813.2942.36.camel@linuxfoundation.org> (raw)
In-Reply-To: <a04373f5-cb03-25a3-36fa-da92b0cdd71d@gmail.com>
On Fri, 2018-04-06 at 13:46 -0700, akuster808 wrote:
> Shouldn't Master get all these changes first then we switch to stable
> branch when we have a new release?
>
> My German genes are raging about "Rules" ; )
master did get them?
To be really clear, "master" is never a value that would appear in
LAYERSERIES. That would let everyone be lazy and master would match
everywhere, then this would all be pointless.
Early in the next cycle I'll add "thud" to the list in OE-Core master
branch. Later in the cycle, when we make more invasive changes which
break compatibility, I'll drop "sumo". At that point people who haven't
added "thud" will start to see errors but this should all work out
earlier in the cycle than happened this time around.
It was a choice of doing this now, or wait another six months to get
started and since we have had the variables for a while I've opted to
move us forward on this. I'd already had comments that "rocko" in
layer.conf was incorrect, which it was and changing that was always
going to cause some pain.
Cheers,
Richard
next prev parent reply other threads:[~2018-04-06 21:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:37 LAYERSERIES Richard Purdie
2018-04-06 14:16 ` [Openembedded-architecture] LAYERSERIES Trevor Woerner
2018-04-06 15:29 ` Richard Purdie
2018-04-06 18:16 ` Scott Rifenbark
2018-04-06 22:25 ` Richard Purdie
2018-04-06 22:44 ` Scott Rifenbark
2018-04-07 14:13 ` Richard Purdie
2018-04-06 18:25 ` Martin Jansa
2018-04-06 22:00 ` Richard Purdie
2018-04-06 20:46 ` akuster808
2018-04-06 21:56 ` Richard Purdie [this message]
2018-04-14 21:48 ` Trevor Woerner
2018-04-15 21:12 ` Richard Purdie
2018-04-06 18:58 ` Denys Dmytriyenko
2018-04-06 21:52 ` Richard Purdie
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=1523051813.2942.36.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=alexander.kanavin@intel.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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