public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Thu, 7 Nov 2013 12:13:27 +0100	[thread overview]
Message-ID: <20131107121327.06404af1@lilith> (raw)
In-Reply-To: <527B6DCC.80605@denx.de>

Hi Heiko,

On Thu, 07 Nov 2013 11:39:08 +0100, Heiko Schocher <hs@denx.de> wrote:


> >> Right, boards.cfg gets unhandy ... Hmm .. what with the column
> >> "Staus" ... instead of "Active" it would be more informative to have
> >> there the livetime counter, and a single digit saves some characters ;-)

I'm not sure we need to save characters from boards.cfg.

Note also that one goal of boards.cfg is to not have multiple files
around that have to remain consistent.

Still :

> > I can't understand the status field at all, just for the record ;)
> 
> Hmm.. good question ...

There has been some discussion on this already; indeed, the status
field is not really aptly named or defined and should be reworked.

We could, for instance, have a "Last tested" field instead of the
"Active" field.

> Ok, two decisions:
> 
> - Do we want to collect board testinginformation?

I'd say we might want to, if only because it tells us if a board
maintainer is still active or not, instead of finding out long later.

> - Do we want to delete old boards automatically after we do not get
>    some test reports after a time intervall?

I don't, at least, not without a long enough period during which the
board remains in "unmaintained" state. E.g., for each release, the list
of "unmaintained" boards is produced along with the release notes, and
boards which are still "unmaintained" when nearing the next release
(roughly 90 days later) get deleted right before the new release.

> bye,
> Heiko

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-11-07 11:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 13:05 [U-Boot] livetime of boards Heiko Schocher
2013-11-05 20:37 ` Tom Rini
2013-11-06  7:50   ` Wolfgang Denk
2013-11-07  8:17     ` Heiko Schocher
2013-11-07  9:37       ` Andreas Bießmann
2013-11-07 10:39         ` Heiko Schocher
2013-11-07 11:13           ` Albert ARIBAUD [this message]
2013-11-07 11:42             ` Heiko Schocher
2013-11-07 12:06               ` Wolfgang Denk
2013-11-07 12:21                 ` Heiko Schocher
2013-11-07 11:24           ` Andreas Bießmann
2013-11-07 11:52             ` Heiko Schocher
2013-11-07 12:12               ` Wolfgang Denk
2013-11-07 12:50                 ` Heiko Schocher
2013-11-07 19:19                   ` Wolfgang Denk
2013-11-08  5:31                     ` Heiko Schocher
2013-11-08  7:19                       ` Wolfgang Denk
2013-11-07 12:01             ` Wolfgang Denk
2013-11-07 12:16               ` Andreas Bießmann
2013-11-07 12:46               ` Heiko Schocher
2013-11-07 19:15                 ` Wolfgang Denk
2013-11-08  5:28                   ` Heiko Schocher
2013-11-08  6:20                     ` Wolfgang Denk
2013-11-08  7:11                       ` Heiko Schocher
2013-11-07 13:31         ` Tom Rini
2013-11-07 14:27           ` Andreas Bießmann
2013-11-07 19:26           ` Wolfgang Denk
2013-11-07 20:51             ` Tom Rini
2013-11-07 21:06               ` Wolfgang Denk
2013-11-08  5:35             ` Heiko Schocher
2013-11-08  4:58           ` Heiko Schocher

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=20131107121327.06404af1@lilith \
    --to=albert.u.boot@aribaud.net \
    --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