From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Custodians] [ANN] U-Boot v2020.01-rc4 released
Date: Tue, 3 Dec 2019 18:00:11 +0100 [thread overview]
Message-ID: <581da7d9-1ca8-2fab-9a11-2f4fd290194b@denx.de> (raw)
In-Reply-To: <CAPnjgZ2pQJJ2TRAxhdhdbBAyzZ7dNBLhTEE=RCqwz=SrgSz24Q@mail.gmail.com>
On 12/3/19 5:52 PM, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 2 Dec 2019 at 20:11, Tom Rini <trini@konsulko.com> wrote:
>>
>> Hey all,
>>
>> It's release day and here is v2020.01-rc4. Yes, I'm still working on
>> fixing all of the issues that pop up as I get the MTD clean-up series
>> ready to go. In fact, what I need to do at this point is grab the
>> handful of size reduction patches that this has shown are worthwhile,
>> then I can do the MTD series. Then we're down to just fixing up
>> misconversions where things got turned off.
>>
>> Once again, for a changelog,
>> git log --merges v2020.01-rc3..v2020.01-rc4
>> and as always, I ask for more details in the PRs people send me so I can
>> put them in the merge commit.
>>
>> I'm planning on doing -rc5 on December 23rd with the release scheduled
>> on January 6th. Thanks all!
>
> Speaking of next year, what is the plan for the release. Is there any
> chance we might move back to a release every two months? The
> three-month process is very slow...
I am very happy with this 3-month release cycle, it's less stressful and
I think the quality of the releases is higher too.
next prev parent reply other threads:[~2019-12-03 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 3:10 [U-Boot] [ANN] U-Boot v2020.01-rc4 released Tom Rini
[not found] ` <73b453a4-ed9c-3177-6623-0ce716cc31a8@microchip.com>
2019-12-03 11:55 ` [U-Boot-Custodians] " Eugen.Hristev at microchip.com
2019-12-03 14:30 ` Tom Rini
2019-12-03 16:45 ` Joe Hershberger
2019-12-03 17:05 ` Tom Rini
2019-12-03 20:56 ` Joe Hershberger
2019-12-03 21:03 ` Tom Rini
2019-12-03 16:52 ` Simon Glass
2019-12-03 17:00 ` Marek Vasut [this message]
2019-12-03 17:07 ` Tom Rini
2019-12-03 17:20 ` Simon Glass
2019-12-03 17:41 ` 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=581da7d9-1ca8-2fab-9a11-2f4fd290194b@denx.de \
--to=marex@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.