From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.11-rc1 released
Date: Tue, 4 Oct 2016 15:10:08 +0200 [thread overview]
Message-ID: <57F3AA30.8090109@denx.de> (raw)
In-Reply-To: <20161004122931.GH4884@bill-the-cat>
Hello Tom,
Am 04.10.2016 um 14:29 schrieb Tom Rini:
> On Tue, Oct 04, 2016 at 07:52:35AM +0200, Heiko Schocher wrote:
>> Hello Tom,
>>
>> Am 03.10.2016 um 15:39 schrieb Tom Rini:
>>> Hey all,
>>>
>>> It's release day and v2016.11-rc1 is out and the merge window is closed.
>>> I've updated git and the tarballs are also up now.
>>>
>>> I plan on doing -rc2 on the 17th. I know there's a good chunk of my
>>> patchwork queue that needs going over and bringing in, and I shall soon.
>>>
>>> Thanks all!
>>
>> Thanks for your work!
>>
>> Release works on the following boards:
>>
>> arch board
>> AT91 : corvus and smartweb
>> am335x : shc
>> mpc5200: tqm5200
>>
>> see:
>> http://xeidos.ddns.net/tests/test_db_auslesen.php#102
>> and newer IDs ...
>
> Nice!
>
>> BTW:
>> The cyclic tests run each monday morning between 03:00 +0200 and 06:00
>> +0200, so if you do a release before, you can look if it works on
>> this boards on monday morning ;-)
>
> I don't think I'm likely to move up to a Sunday release schedule but...
> if you move that window to Tuesday it should always catch releases :)
I selected monday nights for automated tests, as this is the time with
the lowest traffic in our lab ... but yes, why not, I moved the tests
to tuesday nights.
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:[~2016-10-04 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 13:39 [U-Boot] [ANN] U-Boot v2016.11-rc1 released Tom Rini
2016-10-04 5:52 ` Heiko Schocher
2016-10-04 12:29 ` Tom Rini
2016-10-04 13:10 ` 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=57F3AA30.8090109@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