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: Re: [ANN] U-Boot v2025.04 released
Date: Tue, 8 Apr 2025 08:20:55 -0600	[thread overview]
Message-ID: <20250408142055.GW5495@bill-the-cat> (raw)
In-Reply-To: <20250407220011.GS5495@bill-the-cat>

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

On Mon, Apr 07, 2025 at 04:00:11PM -0600, Tom Rini wrote:
> Hey all,
> 
> It's release day and here's v2025.04. We had some last minute issues
> reported, but then also resolved.  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 v2025.04-rc5..v2025.04
> contains what I've pulled since the last RC or:
> git log --merges v2025.01..v2025.04
> 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.
> 
> As is becoming reguarly scheduled, we have a community meeting tomorrow
> (for me anyhow). The meeting details itself are:
> https://meet.google.com/btj-wgcg-euw
> April 7th, 2025. 9am (GMT -06:00)

Sigh. As Marek pointed out on IRC, I got the date wrong in the email.
It's today, in about 40 minutes. Sorry for the confusion all.

-- 
Tom

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

  reply	other threads:[~2025-04-08 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 22:00 [ANN] U-Boot v2025.04 released Tom Rini
2025-04-08 14:20 ` Tom Rini [this message]
2025-04-09 13:46 ` Community meeting April 8th 2025 (was: Re: [ANN] U-Boot v2025.04 released) Caleb Connolly
2025-04-10 14:14   ` Raymond Mao

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=20250408142055.GW5495@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