From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2017.03-rc3 released
Date: Tue, 28 Feb 2017 12:33:38 +0100 [thread overview]
Message-ID: <58B56012.50800@denx.de> (raw)
In-Reply-To: <20170228003809.GE20531@bill-the-cat>
Hello Tom,
Am 28.02.2017 um 01:38 schrieb Tom Rini:
> Hey all,
>
> It's release day and v2017.03-rc3 is out. All in all, I'm OK with the
> contents here. It's the week after ELC, and you might have noticed I've
> been more picky today about PRs than I have in the past. During the
> "Linus and Dirk show" keynote, Linus brought up, as they'd just gone
> past some milestone year in the "new" release cycle model, it took them
> maybe 5 years to get to the point where everyone knows what is and isn't
> allowed at various points in the release cycle. So I'm going to try and
> be better, quicker. Once -rc2 is out, the window really has closed for
> "been around for a bit, stable now, missed the -rc1 cut off tho". There
> will always be another merge window, and on a rather predictable
> schedule too.
>
> Something else I want to point out now is that we have a few
> architectures that have not seen a lot of activity in the last few
> years, aren't functional to varying degrees and don't have a
> non-bouncing maintainer address. Between then and now, I'm going to try
> one last time to contact people associated with a few architectures and
> then I'm going to remove them after v2017.03 is out.
>
> As a final note, I expect us to release v2017.03 on schedule on the 13th
> of March.
>
> Thanks all!
I miss patch:
http://patchwork.ozlabs.org/patch/727734/
Without it, ethernet support for at91 boards like the siemens ones,
does not work ...
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2017-02-28 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 0:38 [U-Boot] [ANN] U-Boot v2017.03-rc3 released Tom Rini
2017-02-28 11:33 ` Heiko Schocher [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=58B56012.50800@denx.de \
--to=hs@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