From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: openembedded-core@lists.openembedded.org,
Frederic Martinsons <frederic.martinsons@gmail.com>,
Marta Rybczynska <rybczynska@gmail.com>,
Paul Eggleton <paul.eggleton@linux.microsoft.com>,
Alex Kiernan <alex.kiernan@gmail.com>
Subject: Re: [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes
Date: Wed, 5 Apr 2023 20:40:03 +0200 [thread overview]
Message-ID: <41ad289e-fffb-b9a1-ab53-0c0510c3d324@bootlin.com> (raw)
In-Reply-To: <17531B0D0DFA1CB6.3977@lists.openembedded.org>
Greetings,
I copied the OE-core mailing list to get the attention of contributors.
If you want your new features to be featured in the release and
migration notes for 4.2, it's time to speak!
What I wrote so far is a very early draft meant to help you detect
what's missing and correct what I've written so far.
See my questions and comments below...
On 05.04.23 at 19:46, Michael Opdenacker via lists.openembedded.org wrote:
> diff --git a/documentation/migration-guides/migration-4.2.rst b/documentation/migration-guides/migration-4.2.rst
> index 1339411b3e..3b04e072cb 100644
> ...
> +Rust: mandatory checksums for crates
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +This release now supports checksums for Rust crates and make
> +them mandatory for each crate in a recipe. See :yocto_git:`python3_bcrypt recipe changes
> +</poky/commit/?h=mickledore&id=0dcb5ab3462fdaaf1646b05a00c7150eea711a9a>`
> +for example.
> +
> +The ``cargo-update-recipe-crates`` utility
> +:yocto_git:`has been extended </poky/commit/?h=mickledore&id=eef7fbea2c5bf59369390be4d5efa915591b7b22>`
> +to include such checksums.
Any more Rust changes we should mention in the migration notes?
> diff --git a/documentation/migration-guides/release-notes-4.2.rst b/documentation/migration-guides/release-notes-4.2.rst
> index edafe378b0..1a60fe5490 100644
> --- a/documentation/migration-guides/release-notes-4.2.rst
> +++ b/documentation/migration-guides/release-notes-4.2.rst
Here in the release notes, I didn't work on the detailed changes, such
as version changes for the kernel and many recipes. I'm trying to help
with the first part showing the big picture.
>
> - addpylib ${LAYERDIR}/lib oe
> + addpylib ${LAYERDIR}/lib oe
> +
> +- BitBake has seen multiple internal changes that may impact
> + memory and disk usage as well as parsing time, in particular:
> +
> + - BitBake's Cooker server is now multithreaded.
> +
> + - BitBake's cache has been extended to include more hash
> + debugging data, but has also been optimized to :yocto_git:`compress
> + cache data <https://git.yoctoproject.org/poky/commit/?h=mickledore&id=7d010055e2af3294e17db862f42664ca689a9356>`.
> +
> + - BitBake's Cooker server :yocto_git:`can now be pinged
> + https://git.yoctoproject.org/poky/commit/?h=mickledore&id=26f255da09>`
> + from the UI.
More BitBake changes we should mention?
> +
> +- Rust improvements:
> +
> + - This release adds Cargo support on the target, and includes
> + automated QA tests for this functionality.
> +
> + - It also supports checksums for Rust crates and makes
> + them mandatory for each crate in a recipe.
More Rust changes we should highlight?
> +- Miscellaneous changes:
> +
> + - Supporting 64 bit dates on 32 bit platforms: several packages have been
> + updated to pass Y2038 tests.
By the way, what's the status of Y2038 support in Mickledore? Are all
tests passing now?
To make the drafts easier to review, they have been compiled in the
master-next branch:
https://docs.yoctoproject.org/next/migration-guides/release-4.2.html
Thanks in advance
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2023-04-05 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17531B0D0DFA1CB6.3977@lists.openembedded.org>
2023-04-05 18:40 ` Michael Opdenacker [this message]
2023-04-05 19:04 ` [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes Frédéric Martinsons
2023-04-06 8:23 ` [docs] " Michael Opdenacker
2023-04-06 8:52 ` Frédéric Martinsons
2023-04-06 9:12 ` [PATCH v2] " michael.opdenacker
2023-04-06 10:12 ` [OE-core] " Richard Purdie
2023-04-06 20:53 ` Michael Opdenacker
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=41ad289e-fffb-b9a1-ab53-0c0510c3d324@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=alex.kiernan@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=frederic.martinsons@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.microsoft.com \
--cc=rybczynska@gmail.com \
/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