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 v2024.10 released
Date: Mon, 7 Oct 2024 08:56:51 -0600 [thread overview]
Message-ID: <20241007145651.GU4737@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hey all,
It's release day and so here is v2024.07. We had a few last minute bug
fixes come in, and while I'd prefer they come in earlier in the release
cycle, I'm still happier people are testing before the release comes out
instead of after the release is out. I want to thank everyone that's
contributed to this release, not just in terms of code, but
documentation, testing and otherwise ensuring things go as smoothly as
they can.
In terms of a changelog,
git log --merges v2024.10-rc6..v2024.10
contains what I've pulled since the last RC or:
git log --merges v2024.07..v2024.10
for changes since the last full release. As always, more details in
pull requests (or the tags referenced by them) will result in more
details here.
The merge window is formally open again, and I'll be merging in next
shortly. v2025.01 is scheduled for Monday, January 6th, 2025 and the
merge window will close and -rc1 will be released on the 28nd of
October, and then the next window will open with -rc2, two weeks later.
I'm also trying something slightly different this release and I've put
-rc6 in for Monday, December 30th to have one more tag over the end of
year holidays, to see if that helps with people finding time to test.
We'll how that went in January.
Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next reply other threads:[~2024-10-07 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:56 Tom Rini [this message]
2024-10-08 7:22 ` [ANN] U-Boot v2024.10 released Michal Simek
2024-10-08 17:40 ` Tom Rini
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=20241007145651.GU4737@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox