From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: docs <docs@lists.yoctoproject.org>
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: Start of 4.3 migration guide docs
Date: Wed, 03 May 2023 15:55:44 +0100 [thread overview]
Message-ID: <d7788bbd4dba10c004fa56f0f4160f6c46bfd6f6.camel@linuxfoundation.org> (raw)
As mentioned on the weekly tech call, we need to get better about
documenting changes for the migration guide and release notes as we go
along. Whilst we're not far into 4.3, I realise I made or merged
changes already which will need notes. Since we don't have a guide yet,
let me note them here on the basis Michael will inject them into a new
doc.
* The '-crosssdk' suffix and any MLPREFIX were removed from virtual/XXX
provider/dependencies where a PREFIX was used as well as we don't need
both and it made automated dependency rewriting unnecessarily complex.
In general this only affects internal toolchain dependencies so isn't
end user visible.
* runtime testing of ptest now fails if no test results are returned by
any given ptest.
* the bitbake cooker log now contains notes when the caches are
invalidated which is useful for memory resident bitbake debugging.
* glide was dropped as "go mod" has become the standard
Cheers,
Richard
next reply other threads:[~2023-05-03 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:55 Richard Purdie [this message]
2023-05-03 15:30 ` [docs] Start of 4.3 migration guide docs Michael Opdenacker
2023-05-03 15:44 ` Richard Purdie
2023-05-04 8:46 ` [PATCH] migration-guides: start of 4.3 migration and release notes 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=d7788bbd4dba10c004fa56f0f4160f6c46bfd6f6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.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