From: Alexander Kanavin <alex.kanavin@gmail.com>
To: michael.opdenacker@bootlin.com
Cc: OE-core <openembedded-core@lists.openembedded.org>,
YP docs mailing list <docs@lists.yoctoproject.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] Call for contributions to the 5.0 release notes
Date: Mon, 18 Mar 2024 14:19:45 +0100 [thread overview]
Message-ID: <CANNYZj8KxPxPxmLDQrOgMAXo8csysaz6u4Upd07=MCv23M9D9g@mail.gmail.com> (raw)
In-Reply-To: <f53c085e-3d24-42d3-ba62-e1c543311dd1@bootlin.com>
So I have looked through my commits over the past year that
*definitely* need documenting, and identified these standouts:
- https://git.yoctoproject.org/poky/commit/?id=63e53fb8b60d38315015844bd3357fa1649cd639
"build-sysroots: target or native sysroot population need to be
selected explicitly"
Easy fix to existing docs, will send asap.
- https://git.yoctoproject.org/poky/commit/?id=2187e823ad66eaaee6a4ed7d748f2c68028a45e7
"selftest/sstatetests: add tests for 'bitbake -S printdiff'"
This functionality needs to be documented; a review of whether there's
something for bitbake-diffsigs (which is related) is also needed. I'll
do this after the first item.
- https://git.yoctoproject.org/poky/commit/?id=6f29e2319cf8f6124de4998e887efab90bc63ba4
"meta/conf/templates/default/conf-summary.txt: add a template summary"
Needs to be documented everywhere where config templates or config
template descriptions are mentioned. Also on todo list.
- https://git.yoctoproject.org/poky/commit/?id=c390b2e615930b60db0d7f3e72d056e0c67ef5bc
"oe-setup-build: add a tool for discovering config templates and
setting up builds"
This was added to master very recently and documenting it is pending
an important fixup:
https://patchwork.yoctoproject.org/project/oe-core/patch/20240305073749.4133403-1-alex@linutronix.de/
which I hope lands in master soon, but for some reason isn't in master-next.
Alex
On Fri, 15 Mar 2024 at 09:12, Michael Opdenacker via
lists.openembedded.org
<michael.opdenacker=bootlin.com@lists.openembedded.org> wrote:
>
> Greetings,
>
> If you contributed new features to the upcoming release, or if you are
> interested in figuring out what's new in 5.0, that would be great if you
> could help us by submitting bits of release notes about them too.
>
> If you are familiar with the Sphinx / ReStructured Text format, you can
> directly send patches against the yocto-docs "master-next" branch
> (https://git.yoctoproject.org/yocto-docs/log/?h=master-next). However,
> I'm also happy to accept raw text as well and format it or even
> elaborate on it by myself.
>
> We may also need proper documentation for the new features, not only
> release notes. I am thinking about documenting the new variables in
> ref-manual/variables.rst, for example.
> Thanks in advance
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#197128): https://lists.openembedded.org/g/openembedded-core/message/197128
> Mute This Topic: https://lists.openembedded.org/mt/104943580/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-03-18 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 8:12 Call for contributions to the 5.0 release notes Michael Opdenacker
2024-03-15 20:58 ` [OE-core] " Ross Burton
2024-03-18 9:44 ` Michael Opdenacker
2024-03-18 13:19 ` Alexander Kanavin [this message]
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='CANNYZj8KxPxPxmLDQrOgMAXo8csysaz6u4Upd07=MCv23M9D9g@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).