From: Matwey V. Kornilov <matwey.kornilov@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] [ANN] U-Boot v2019.07-rc4 released
Date: Sun, 30 Jun 2019 13:32:53 +0300 [thread overview]
Message-ID: <qfa34l$3ar3$1@blaine.gmane.org> (raw)
In-Reply-To: <f558a4ba-3278-3d2c-03a8-64baf2baf0eb@gmx.de>
22.06.2019 22:12, Heinrich Schuchardt пишет:
> On 6/22/19 8:15 PM, Simon Glass wrote:
>> Hi,
>>
>> On Sat, 22 Jun 2019 at 16:10, Andreas Färber <afaerber@suse.de> wrote:
>>>
>>> Hi Simon,
>>>
>>> Am 22.06.19 um 16:55 schrieb Simon Glass:
>>>> I'd like to better understand the benefits of the 3-month timeline.
>>>
>>> It takes time to learn about a release, package and build it, test it on
>>> various hardware, investigate and report errors, wait for feedback and
>>> fixes, rinse and repeat with the next -rc. Many people don't do this as
>>> their main job.
>>>
>>> If we shorten the release cycle, newer boards will get out faster (which
>>> is good) but the overall quality of boards not actively worked on
>>> (because they were working good enough before) will decay, which is bad.
>>> The only way to counteract that would be to automatically test on real
>>> hardware rather than just building, and doing that for all these masses
>>> of boards seems unrealistic.
>>
>> Here I think you are talking about distributions. But why not just
>> take every second release?
>>
>> I have certain had the experience of getting a board our of the
>> cupboard and finding that the latest U-Boot doesn't work, nor the one
>> before, nor the three before that.
>>
>> Are we actually seeing an improvement in regressions? I feel that
>> testing is the only way to get that.
>>
>> Perhaps we should select a small subset of boards which do get tested,
>> and actually have custodians build/test on those for every rc?
>
> What I have been doing before all my recent pull requests is to boot
> both an arm32 (Orange Pi) and and an aarch64 (Pine A64 LTS) board via
> bootefi and GRUB. To make this easier I am using a Raspberry with a
> relay board and a Tizen SD-Wire card (https://wiki.tizen.org/SDWire)
> controlling the system under test,
> cf https://pbs.twimg.com/media/D5ugi3iX4AAh1bn.jpg:large
> What would be needed is scripts to automate the testing including all
> the Python tests.
Is it possible to buy SDwire somewhere?
>
> It would make sense to have such test automation for all of our
> architectures similar to what Kernel CI (https://kernelci.org/) does.
>
> Regards
>
> Heinrich
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
prev parent reply other threads:[~2019-06-30 10:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 1:31 [U-Boot] [ANN] U-Boot v2019.07-rc4 released Tom Rini
2019-06-11 2:56 ` [U-Boot] [U-Boot-Board-Maintainers] " 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 [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='qfa34l$3ar3$1@blaine.gmane.org' \
--to=matwey.kornilov@gmail.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