public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>,
	u-boot-custodians@lists.denx.de,
	u-boot-board-maintainers@lists.denx.de
Subject: Re: [ANN] U-Boot v2022.10-rc1 released
Date: Tue, 26 Jul 2022 13:23:37 +0200	[thread overview]
Message-ID: <1692040.4ee9kKeVGZ@ada> (raw)
In-Reply-To: <20220726003333.GH1146598@bill-the-cat>

Hey hey,

Am Dienstag, 26. Juli 2022, 02:33:33 CEST schrieb Tom Rini:
> Hey all,
> 
> It's release day and so here's v2022.10-rc1.  There's a lot in here, and
> there's a few more things yet to come, hopefully this week, in terms of
> pull requests, and also pulling things out of my own queue.
> 
> One thing I want to call out specifically is the VBE series will be
> coming in soon, so general commentary is welcome and appreciated.  Also,
> we've moved more of our process documentation from the wiki to rst and
> being in-tree.  Patches to clean that up a bit more, or try and clarify
> points about how things work are much appreciated.

Moving the docs to the U-Boot source tree in a renderable format and have it 
available at https://u-boot.readthedocs.io/en/latest/index.html is highly 
appreciated. Thanks to everyone involved in doing that! :-)

Greets
Alex

> 
> In terms of a changelog,
> git log --merges v2022.04..v2022.07-rc1
> 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 October 3rd, 2022.  Thanks all!





      reply	other threads:[~2022-07-26 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  0:33 [ANN] U-Boot v2022.10-rc1 released Tom Rini
2022-07-26 11:23 ` Alexander Dahl [this message]

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=1692040.4ee9kKeVGZ@ada \
    --to=ada@thorsis.com \
    --cc=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