public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stephen Jolley <sjolley.yp.pm@gmail.com>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	",openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)
Date: Fri, 16 Feb 2024 11:34:23 +0000	[thread overview]
Message-ID: <007c20be5b61da1d7752835a3f4775368a76bd97.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAK5yBb8YQoMdR=qKDHPYVUo7jKhRDEjS3Ah6EDccsbdwgmm+Vw@mail.gmail.com>

On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
>  * We are now a week from feature freeze for 5.0, our next LTS
> release

For better or worse but probably not entirely surprisingly, there are
quite a few things that we may want to try and fit in. I've listed them
just so everyone knows what is on the list:

* genericarm64 machine
* add qemuriscv64 tests to the autobuilder, for M3 only
* devtool changes to use git notes
* hashserve improvements
* pending changes in master-next where review is still being worked
* change to rust test suite logging
* devtool IDE changes

Also things which are worrying:

* Rust upgrade blocked by reproducibility issues
* musl upgrade blocked by large number of unsubmitted pending patches
* nativesdk-systemd usage broken by usrmerge requirement (we're not 
  changing the SDK layout days before freeze)

I'm sure there are some things I'm forgetting too.

Please let me know ASAP if there is anything else pending.

The good news is that several problematic issues do seem to be finding
resolutions in the last 48h.

Cheers,

Richard








  reply	other threads:[~2024-02-16 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 15:50 Yocto Project Status 13 February 2024 (WW07) Stephen K Jolley
2024-02-16 11:34 ` Richard Purdie [this message]
2024-02-16 13:12   ` [OE-core] " Jose Quaresma
2024-02-16 13:33     ` Richard Purdie
2024-02-16 14:04       ` Alexander Kanavin
2024-02-19 12:09   ` Alexander Kanavin

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=007c20be5b61da1d7752835a3f4775368a76bd97.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto@lists.yoctoproject.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