Re: [OE-core] Yocto Project Status 13 February 2024 (WW07)

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2024-02-16 at 13:12 +0000, Jose Quaresma wrote:
> 
> 
> Richard Purdie <richard.purdie@linuxfoundation.org> escreveu (sexta,
> 16/02/2024 à(s) 11:34):
> > 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.
> 
> I think it would also be important to update the golang toolchain
> from the 1.20.x
> we haven't done it yet the 1.21 and 1.22.
> I intend to dedicate some time to 1.21 but I can't promise anything
> and there is a
> high probability that I won't be able to correct the problems that
> exist.

Whilst I agree that would be nice, I have no knowledge in that area, no
available time and nobody else seems to have that either. Not sure what
we can do in that case :(

Cheers,

Richard