From: Paul Eggleton <bluelightning@bluelightning.org>
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 0/9] Updates for the 5.0 release
Date: Sun, 14 Apr 2024 13:43:09 -0700 [thread overview]
Message-ID: <cover.1713127068.git.bluelightning@bluelightning.org> (raw)
Updates for the 5.0 release on top of master-next, including release
notes and migration guide, as well as adjustments for the rest of the
documentation. I think we are still missing a few changes but
unfortunately I've run out of time. Thanks to all who added content
ahead of me though!
The following changes since commit 4b839c460867d685584134dbd322cd9b20f2ae6d:
release-notes-5.0: various additions and improvements (2024-04-12 15:08:40 +0200)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib paule/5.0-release
https://git.yoctoproject.org/poky-contrib/log/?h=paule/5.0-release
Paul Eggleton (9):
ref-manual: Add virtual-slash QA check
ref-manual: add new python classes
classes: cve_check: add note about remote patches
variables: add TARGET_DBGSRC_DIR
dev-manual: update reference to sstate-cache-management script
dev-manual: update custom distribution section
release-notes: Add CVEs, recipe upgrades and contributors for 5.0
migration: Extend migration guide for 5.0
release-notes: additional features and one known issue for 5.0
.../dev-manual/custom-distribution.rst | 34 +-
documentation/dev-manual/disk-space.rst | 2 +-
.../migration-guides/migration-5.0.rst | 62 +-
.../migration-guides/release-notes-5.0.rst | 635 +++++++++++++++++-
documentation/ref-manual/classes.rst | 31 +
documentation/ref-manual/qa-checks.rst | 8 +
documentation/ref-manual/variables.rst | 4 +
7 files changed, 757 insertions(+), 19 deletions(-)
--
2.25.1
next reply other threads:[~2024-04-14 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 20:43 Paul Eggleton [this message]
2024-04-14 20:43 ` [PATCH 1/9] ref-manual: Add virtual-slash QA check Paul Eggleton
2024-04-14 20:43 ` [PATCH 2/9] ref-manual: add new python classes Paul Eggleton
2024-04-15 13:43 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 3/9] classes: cve_check: add note about remote patches Paul Eggleton
2024-04-14 20:43 ` [PATCH 4/9] variables: add TARGET_DBGSRC_DIR Paul Eggleton
2024-04-14 20:43 ` [PATCH 5/9] dev-manual: update reference to sstate-cache-management script Paul Eggleton
2024-04-14 20:43 ` [PATCH 6/9] dev-manual: update custom distribution section Paul Eggleton
2024-04-15 14:04 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 7/9] release-notes: Add CVEs, recipe upgrades and contributors for 5.0 Paul Eggleton
2024-04-15 14:24 ` Michael Opdenacker
2024-04-18 14:47 ` [docs] " Paul Eggleton
2024-04-18 15:26 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 8/9] migration: Extend migration guide " Paul Eggleton
2024-04-15 14:41 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 9/9] release-notes: additional features and one known issue " Paul Eggleton
2024-04-15 8:06 ` [docs] " Quentin Schulz
2024-04-15 15:22 ` Michael Opdenacker
2024-04-18 14:50 ` Paul Eggleton
2024-04-15 15:41 ` Michael Opdenacker
2024-04-15 15:43 ` [PATCH 0/9] Updates for the 5.0 release 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=cover.1713127068.git.bluelightning@bluelightning.org \
--to=bluelightning@bluelightning.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).