public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 v2025.01 released
Date: Mon, 6 Jan 2025 18:55:44 -0600	[thread overview]
Message-ID: <20250107005544.GG3476@bill-the-cat> (raw)

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

Hey all,

It's late in the day, but here's v2025.01. Note that this isn't late due
to any issues with the master branch but rather because I've been
bisect'ing a stubborn issue in -next. Our January release is always
tricky due to holidays, but the extra -rc may have helped. We won't
really know I suspect however until much later this month when even more
testing happens post release.  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.01-rc6..v2025.01
contains what I've pulled since the last RC or:
git log --merges v2024.10..v2025.01
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. However, I'm going to hold off
on merging -next as I'm bisect'ing an issue there still and want to sort
that out before merging. I'll post about that on it's own soon.
The v2025.04 release is scheduled for Monday, April 7th, 2025 and the
merge window will close and -rc1 will be released on the 27th of
January, and then the next window will open with -rc2, two weeks later.

Thanks all!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

                 reply	other threads:[~2025-01-07  0:55 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=20250107005544.GG3476@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