($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com,
	Joao Marcos Costa <joaomarcos.costa@bootlin.com>
Subject: [PATCH v1 0/5] Update migration-guides and release-notes
Date: Wed,  3 Apr 2024 16:37:19 +0200	[thread overview]
Message-ID: <20240403143724.1956838-1-joaomarcos.costa@bootlin.com> (raw)

Hello,

I started inspecting the changes since Nanbield to come out with a bit of
documentation for the upcoming release. Here are my first writings, and I count
on doing some more, as WIC enhancements, testing and scripts' enhancements, Go
language, etc.

Best regards,

Joao Marcos Costa (5):
  migration-guides: list removed recipes
  migration-guides: leave Removed classes empty
  migration-guides: leave Deprecated variables empty
  migration-guides: list systemd changes
  release-notes: list systemd changes

 documentation/migration-guides/migration-5.0.rst  | 15 +++++++++++++--
 .../migration-guides/release-notes-5.0.rst        | 11 +++++++++++
 2 files changed, 24 insertions(+), 2 deletions(-)

-- 
2.43.0



             reply	other threads:[~2024-04-03 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 14:37 Joao Marcos Costa [this message]
2024-04-03 14:37 ` [PATCH v1 1/5] migration-guides: list removed recipes Joao Marcos Costa
2024-04-03 14:37 ` [PATCH v1 2/5] migration-guides: leave Removed classes empty Joao Marcos Costa
2024-04-03 14:37 ` [PATCH v1 3/5] migration-guides: leave Deprecated variables empty Joao Marcos Costa
2024-04-03 14:37 ` [PATCH v1 4/5] migration-guides: list systemd changes Joao Marcos Costa
2024-04-03 14:37 ` [PATCH v1 5/5] release-notes: " Joao Marcos Costa
2024-04-04 14:41 ` [docs] [PATCH v1 0/5] Update migration-guides 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=20240403143724.1956838-1-joaomarcos.costa@bootlin.com \
    --to=joaomarcos.costa@bootlin.com \
    --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).