U-Boot Archive on lore.kernel.org
 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.04-rc5 released
Date: Mon, 24 Mar 2025 20:01:30 -0600	[thread overview]
Message-ID: <20250325020130.GF93000@bill-the-cat> (raw)

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

Hey all,

So it's release day and I have tagged and pushed things out. This will
be merged to -next shortly.

One thing to note is that just today a bug was reported due to a missing
'fallthrough;' line and in turn we need to fix that in a number of
places and ensure it doesn't return. This will happen between now and
the release as I think it's clear enough.

While we have been having regular meetings after an -rc release, I have
assorted personal appointments this week and need to reschedule for next
week instead.

Repeating what I said on the -rc3 release,
I've been looking in to seeing how we could get modern project
governance setup and some umbrella organization to handle financial
matters, etc. To that end, I've been talking with the Software Freedom
Conservancy (https://sfconservancy.org/). I continue to need to post a
bit longer of an email explaining my thoughts and looking for volunteers
to help with organization.

In terms of a changelog, 
git log --merges v2025.04-rc4..v2025.04-rc5
As always, more details in pull requests (or the tags referenced by
them) will result in more details here.

I plan to have the final release will be 07 April 2025.

Thanks all!

-- 
Tom

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

             reply	other threads:[~2025-03-25  2:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  2:01 Tom Rini [this message]
2025-03-25  9:17 ` [ANN] U-Boot v2025.04-rc5 released Mattijs Korpershoek
2025-03-25 14:51   ` Tom Rini
2025-04-02 23:53 ` 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=20250325020130.GF93000@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