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/[email protected]/
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
<[email protected]> 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 (#197306): 
https://lists.openembedded.org/g/openembedded-core/message/197306
Mute This Topic: https://lists.openembedded.org/mt/104943580/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to