From: Paul Eggleton <paul.eggleton@linux.microsoft.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 0/9] Release documentation for 4.0
Date: Thu, 21 Apr 2022 18:40:33 -0700 [thread overview]
Message-ID: <cover.1650591341.git.paul.eggleton@linux.microsoft.com> (raw)
Release notes, migration guide and related changes for the
4.0 release.
(Note that the "Repositories / Downloads" section of the release notes
still needs to be filled in.)
The following changes since commit 4755961bbb5f674a7532b91cca20ea44a1e22ae7:
docs: sphinx-static: switchers.js.in: do not mark branches as outdated (2022-04-20 17:24:31 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/4.0-release
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/4.0-release
Paul Eggleton (9):
migration-3.4: add missing entry on EXTRA_USERS_PARAMS
ref-manual: add a note about hard-coded passwords
ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE
ref-manual: add mention of vendor filtering to CVE_PRODUCT
ref-manual: add KERNEL_DEBUG_TIMESTAMPS
ref-manual: add XZ_THREADS and ZSTD_THREADS
ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS*
migration-guides: complete migration guide for 4.0
migration-guides: add release notes for 4.0
documentation/migration-guides/migration-3.4.rst | 7 +
documentation/migration-guides/migration-4.0.rst | 345 +++++---
.../migration-guides/release-notes-4.0.rst | 864 +++++++++++++++++++++
documentation/ref-manual/classes.rst | 12 +
documentation/ref-manual/qa-checks.rst | 10 +-
documentation/ref-manual/variables.rst | 48 +-
6 files changed, 1161 insertions(+), 125 deletions(-)
create mode 100644 documentation/migration-guides/release-notes-4.0.rst
--
1.8.3.1
next reply other threads:[~2022-04-22 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 1:40 Paul Eggleton [this message]
2022-04-22 1:40 ` [PATCH 1/9] migration-3.4: add missing entry on EXTRA_USERS_PARAMS Paul Eggleton
2022-04-22 10:30 ` [docs] " Quentin Schulz
2022-04-22 10:41 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 2/9] ref-manual: add a note about hard-coded passwords Paul Eggleton
2022-04-22 9:35 ` [docs] " Peter Kjellerstedt
2022-04-22 1:40 ` [PATCH 3/9] ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE Paul Eggleton
2022-04-22 9:37 ` [docs] " Peter Kjellerstedt
2022-04-22 1:40 ` [PATCH 4/9] ref-manual: add mention of vendor filtering to CVE_PRODUCT Paul Eggleton
2022-04-22 1:40 ` [PATCH 5/9] ref-manual: add KERNEL_DEBUG_TIMESTAMPS Paul Eggleton
2022-04-22 1:40 ` [PATCH 6/9] ref-manual: add XZ_THREADS and ZSTD_THREADS Paul Eggleton
2022-04-22 10:40 ` [docs] " Quentin Schulz
2022-04-22 11:46 ` Richard Purdie
2022-04-22 12:47 ` Quentin Schulz
2022-04-22 12:50 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 7/9] ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS* Paul Eggleton
2022-04-22 9:50 ` [docs] " Peter Kjellerstedt
2022-04-22 10:51 ` Quentin Schulz
2022-04-22 1:40 ` [PATCH 8/9] migration-guides: complete migration guide for 4.0 Paul Eggleton
2022-04-22 11:10 ` [docs] " Quentin Schulz
2022-04-22 12:09 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 9/9] migration-guides: add release notes " Paul Eggleton
2022-04-22 11:17 ` [docs] " Quentin Schulz
2022-04-22 11:18 ` [docs] [PATCH 0/9] Release documentation " Quentin Schulz
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.1650591341.git.paul.eggleton@linux.microsoft.com \
--to=paul.eggleton@linux.microsoft.com \
--cc=docs@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