From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: u-boot-custodians@lists.denx.de, u-boot-board-maintainers@lists.denx.de
Subject: [ANN] U-Boot v2022.04-rc3 released
Date: Mon, 28 Feb 2022 18:03:34 -0500 [thread overview]
Message-ID: <20220228230334.GA5020@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hey all,
It's release day and so here's v2022.04-rc3. With the release itself
nearing a month away, I'm opening the -next branch as well with this
release. At this point, if there's platform specific changes, or other
bug fixes / changes you had submitted and hoped would be in this
release, but are not there yet, please feel free to follow up to those
patches so they don't get lost.
In terms of a changelog,
git log --merges v2022.04-rc2..v2022.04-rc3
contains what I've pulled but as always, better PR messages and tags
will provide better results here.
So we're now looking at regular releases every other Monday, and with
final release on April 4th, 2022. Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
reply other threads:[~2022-02-28 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220228230334.GA5020@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.