Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Scott Rifenbark <srifenbark@gmail.com>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: 2.6 migration guide
Date: Fri, 2 Nov 2018 15:10:15 +0000	[thread overview]
Message-ID: <59badcade81f4c09bc8d71210d2e7019@XBOX04.axis.com> (raw)
In-Reply-To: <CAFNP8OvFy2n7SMe5de66EcdM3URFm-b+dpcqS09hW0CMa9rNaA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]

In “4.14.2. OpenSSL Changes”, change “both versions their dependency chains” to “both versions in their dependency chains”.
In “4.14.4. Security Changes”, change “files” to “flags” (twice).

//Peter

From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> On Behalf Of Scott Rifenbark
Sent: den 30 oktober 2018 23:07
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>; openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] 2.6 migration guide

Paul,

Thanks for sending.

Contributors....

I have an initial section at https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release, which is based on Richard's input.  I am sure there are more items.

Thanks,
Scott

On Tue, Oct 23, 2018 at 2:14 PM Paul Eggleton <paul.eggleton@linux.intel.com<mailto:paul.eggleton@linux.intel.com>> wrote:
Hi folks

When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of such changes in master for
upcoming 2.6 (thud) make a note of it on the wiki in raw form on this page:

  https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

Scott and I will take care of cleaning it up, so things added there don't need
to be perfect.

I will also be doing my usual trawl through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.

Thanks,
Paul

--
Paul Eggleton
Intel Open Source Technology Centre


[-- Attachment #2: Type: text/html, Size: 6049 bytes --]

  parent reply	other threads:[~2018-11-02 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 21:14 2.6 migration guide Paul Eggleton
2018-10-30 22:06 ` Scott Rifenbark
     [not found]   ` <25f056c7-d6ba-499f-8bf4-b8d1470fff4b@gmail.com>
2018-10-31 15:33     ` [yocto] " Scott Rifenbark
2018-10-31 15:50     ` Scott Rifenbark
2018-10-31 16:01       ` Bas Mevissen
2018-10-31 16:56         ` Scott Rifenbark
2018-11-02 15:10   ` Peter Kjellerstedt [this message]
2018-11-02 15:48     ` Scott Rifenbark
2018-11-05  3:32   ` Paul Eggleton
2018-11-08 22:41     ` [yocto] " Paul Eggleton
2018-11-08 22:50       ` Paul Eggleton

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=59badcade81f4c09bc8d71210d2e7019@XBOX04.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=srifenbark@gmail.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