U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2021.04-rc5 released
Date: Mon, 29 Mar 2021 17:25:21 -0400	[thread overview]
Message-ID: <20210329212521.GP1310@bill-the-cat> (raw)

Hey all,

It's release day, and here's v2021.04-rc5.  Once again, not a whole lot
of change since last time in master, and -next has been and is still
open.  I just want to repeat a few things from -rc4:

- We've moved from "gitlab.denx.de" (and also "git.denx.de") to
  "source.denx.de", please make sure to update your scripts and tools
  and so forth.  If you send me pull requests, now is a good time to
  switch to url/pushurl if you haven't already.
- Once v2021.04 is released I will be pushing a large number of board
  removals for things that will be then 2 years past their "migrate this
  by ... or it might be removed" date which is also around 3 years total
  of notice.

A new notice would be that we've added a migration warning of v2022.04
for DM_I2C.  This migration is largely done already and there's only a
few boards that need intervention still.

In terms of a changelog, 
git log --merges v2021.04-rc4..v2021.04-rc5
contains what I've pulled but as always, better PR messages and tags
will provide better results here.

I'll be merging -rc5 in to -next shortly and pushing that out as well
once CI completes.

This is the final -rc before release on April 5th.  Thanks all!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210329/36103bce/attachment.sig>

                 reply	other threads:[~2021-03-29 21:25 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=20210329212521.GP1310@bill-the-cat \
    --to=trini@konsulko.com \
    --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