[OE-core] 2.6 planning proposals and meeting

[Scott Rifenbark]

Hi Peter,

Thanks for the patch.  I have applied it to the 2.5 version of the Yocto
Project Reference Manual (see
https://yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-BUILDHISTORY_FEATURES).
You can also see
https://yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-BUILDHISTORY_FEATURES
for the commit in the yocto-docs repository.

Please look it over as I did a bit of modification for manual purposes.

Regards,
Scott

On Thu, May 3, 2018 at 12:29 AM, Peter Kjellerstedt <
peter.kjellerstedt at axis.com> wrote:

>
>
>
>
> *From:* openembedded-core-bounces at lists.openembedded.org [mailto:
> openembedded-core-bounces at lists.openembedded.org] *On Behalf Of *Scott
> Rifenbark
> *Sent:* den 1 maj 2018 16:56
> *To:* Richard Purdie <richard.purdie at linuxfoundation.org>
> *Cc:* openembedded-core <openembedded-core at lists.openembedded.org>
> *Subject:* Re: [OE-core] 2.6 planning proposals and meeting
>
>
>
> On Tue, May 1, 2018 at 7:46 AM, Richard Purdie <richard.purdie@
> linuxfoundation.org> wrote:
>
> Hi,
>
> On Fri, 2018-04-20 at 08:02 -0400, Daniel F. Dickinson wrote:
> > I'm relatively new to OE; I've written a couple of pre-alpha layers
> > to try some idea, and worked on meta-openembedded, but I've not had a
> > chance to go in depth on the Yocto documentation, and at the some
> > there see to be things (based on the lists) that are out of date, or
> > new things that aren't even mentioned, which makes getting up speed
> > somewhat difficult.
>
> Writing down where you think there are issues would be a help so that
> we can see if there is some way we can improve that.
>
>
>
> Yes - please indicate any areas in the documentation you believe need
> updated, changed, or added.  I have been trying to bring things up-to-date
> in several manuals during the 2.5 process.  So, identifying areas in the
> 2.5 manual set would be very helpful.  To be sure you are viewing 2.5
> manuals use the following form for the URL:
>
>       yoctoproject.org/docs/2.5/<manual_folder>/<manual_folder>.html
>
>       where <manual_folder> is
>
>            brief-yoctoprojectqs
>
>            bsp-guide
>
>            overview-manual
>
>            dev-manual
>
>            sdk-manual
>
>            profile-manual
>
>            kernel-dev
>
>            ref-manual
>
>            toaster-manual
>
>            bitbake-user-guide
>
> Thanks
>
> Scott
>
> Is there any special process to get manual updates accepted? I am asking
> because I sent an update for the BUILDHISTORY_FEATURES variable to the
> Yocto mailing list (https://lists.yoctoproject.org/pipermail/yocto/2018-
> January/039787.html) at the end of January (last pinged a month ago) and
> it still has not made it into the manual AFAICT and it has not received any
> feedback.
>
> //Peter
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180503/7b35fefe/attachment-0002.html>