From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2019.07-rc4 released
Date: Mon, 10 Jun 2019 21:31:47 -0400 [thread overview]
Message-ID: <20190611013147.GW7115@bill-the-cat> (raw)
Hey all,
It's release day and here is v2019.07-rc4. At this point, I know we
have some regression fixes for i.MX that are coming, and I'm expecting a
fix to the build time failure for tinker-rk3288.
To repeat myself about DM migration deadlines, first, let me say again,
that DM is not required for SPL. This comes up enough that I want to
say it again here. Next, if there is active progress on converting
things, we'll keep from pulling the code out. This is why for example,
we haven't yet pulled out a lot of deprecated SPI code. Some of it is
still in progress on being converted, so I need to update the series I
posted after the last -rc to remove still less drivers.
In terms of a changelog,
git log --merges v2019.07-rc3..v2019.07-rc4
continues to improve in quality. If you're sending me a PR, please
include a few lines or words in summary and I'll be sure to put it into
the merge commit.
As I mentioned with -rc3, with this cycle is coming closer to an end,
it's time to decide if we're going to keep this 3 month cycle or go back
to 2 months. After the last release while I did get some feedback, the
overall balance is still in the 3 month bucket.
I'm planning on doing -rc5 on June 24th with the release scheduled on
July 8th. Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190610/e6b9a846/attachment.sig>
next reply other threads:[~2019-06-11 1:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 1:31 Tom Rini [this message]
2019-06-11 2:56 ` [U-Boot] [U-Boot-Board-Maintainers] [ANN] U-Boot v2019.07-rc4 released Marek Vasut
2019-06-11 11:15 ` Tom Rini
2019-06-11 13:39 ` Marek Vasut
2019-06-11 5:38 ` Lukasz Majewski
2019-06-16 17:36 ` [U-Boot] Poplar broken in U-Boot v2019.07-rc4 Andreas Färber
2019-06-17 2:16 ` Shawn Guo
2019-06-17 2:19 ` Bin Meng
2019-06-17 2:31 ` Shawn Guo
2019-06-22 14:55 ` [U-Boot] [ANN] U-Boot v2019.07-rc4 released Simon Glass
2019-06-22 15:08 ` [U-Boot] [U-Boot-Custodians] " Marek Vasut
2019-06-22 15:10 ` [U-Boot] [U-Boot-Board-Maintainers] " Andreas Färber
2019-06-22 18:15 ` Simon Glass
2019-06-22 19:08 ` Andreas Färber
2019-06-22 19:14 ` Simon Glass
2019-06-22 19:49 ` Andreas Färber
2019-06-24 13:56 ` Simon Glass
2019-06-24 17:10 ` [U-Boot] [U-Boot-Custodians] " Marek Vasut
2019-06-25 0:10 ` Simon Glass
2019-06-22 19:12 ` Heinrich Schuchardt
2019-06-22 19:43 ` Marek Vasut
2019-06-24 15:29 ` Tom Rini
2019-06-25 11:10 ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Neil Armstrong
2019-06-25 12:04 ` Tom Rini
2019-06-30 10:34 ` Matwey V. Kornilov
2019-07-01 7:23 ` Neil Armstrong
2019-07-02 16:04 ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Troy Benjegerdes
2019-07-02 17:03 ` Marek Vasut
2019-07-03 15:59 ` Simon Glass
2019-07-03 16:04 ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Tom Rini
2019-07-03 16:22 ` Troy Benjegerdes
2019-07-03 19:34 ` Heinrich Schuchardt
2019-06-25 3:51 ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Heiko Schocher
2019-06-30 10:32 ` Matwey V. Kornilov
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=20190611013147.GW7115@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