[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] 2.6 migration guide
From:       Scott Rifenbark <srifenbark () gmail ! com>
Date:       2018-10-30 22:06:31
Message-ID: CAFNP8OvFy2n7SMe5de66EcdM3URFm-b+dpcqS09hW0CMa9rNaA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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>
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 #5 (text/html)]

<div dir="ltr"><div dir="ltr"><div>Paul,<br></div><div><br></div><div>Thanks for \
sending.   <br></div><div><br></div><div>Contributors....</div><div><br></div><div>I \
have an initial section at <a \
href="https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto \
-project-2.6-release">https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release</a>, \
which is based on Richard&#39;s input.   I am sure there are more \
items.</div><div><br></div><div>Thanks, \
<br></div><div>Scott<br></div></div></div><br><div class="gmail_quote"><div \
dir="ltr">On Tue, Oct 23, 2018 at 2:14 PM Paul Eggleton &lt;<a \
href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks<br> <br>
When Scott prepares the migration guide for a release, he usually looks to me <br>
to collate the notable changes for it (those requiring user intervention). I <br>
haven&#39;t prepared anything yet though and the 2.6 release is fast approaching. \
<br> Can anyone who has been involved in or is aware of such changes in master for \
<br> upcoming 2.6 (thud) make a note of it on the wiki in raw form on this page:<br>
<br>
   <a href="https://wiki.yoctoproject.org/wiki/FutureMigrationGuide" rel="noreferrer" \
target="_blank">https://wiki.yoctoproject.org/wiki/FutureMigrationGuide</a><br> <br>
Scott and I will take care of cleaning it up, so things added there don&#39;t need \
<br> to be perfect. <br>
<br>
I will also be doing my usual trawl through the commits in the release for the <br>
more general changelog, so most things will get picked up that way, but it&#39;s <br>
really helpful if people with first-hand knowledge of the implications of some <br>
of these changes are involved in how they get documented.<br>
<br>
Thanks,<br>
Paul<br>
<br>
-- <br>
Paul Eggleton<br>
Intel Open Source Technology Centre<br>
<br>
<br>
</blockquote></div>



-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[prev in list] [next in list] [prev in thread] [next in thread]