Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18
Date: Wed, 21 Aug 2019 09:51:36 +0200	[thread overview]
Message-ID: <20190821075136.GA12477@scaer> (raw)
In-Reply-To: <b1f6a7dd-7451-ef46-de7c-51efb9a9c38b@mind.be>

Arnout, All,

On 2019-08-20 21:18 +0200, Arnout Vandecappelle spake thusly:
> On 20/08/2019 21:10, Arnout Vandecappelle wrote:
> > On 20/08/2019 00:00, Peter Korsgaard wrote:
> >>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> >>  > "we only show the highest release" -> release-monitoring.org doesn't
> >>  > have the notion of "stable branches" from upstream or anything like
> >>  > that. It even considers -rc versions to be more recent than a regular
> >>  > official release.
> >>
> >>  > But I see your point that anyway release-monitoring.org is only very
> >>  > partially helping to track whether we need to update for security
> >>  > reasons. A CVE-related tracking tool (such as what Matt Weber was
> >>  > working on back then) would be better suited for this task.
> >>
> >>  > If you agree with this, then perhaps the autobuild.b.o/stats/ page, and
> >>  > the corresponding JSON output, should be generated based on the next
> >>  > branch rather than the master branch.
> >>
> >> Presumably only if next exists (and then we have to remember to delete
> >> it as soon as we merge it into master and not just let it linger until
> >> the next release)?
> > 
> >  That would be a good idea anyway. I've known people to be confused by the
> > lingering next branch.
> 
>  Or perhaps it's a better idea to reverse the logic: on -rc1, create the stable
> branch already, and treat master as next. IOW, avoid creating a next at all.

I would argue in favour of this solution.

>  But then we should probably also update the branches info for the autobuilders
> to make sure the stable branch gets sufficient testing.

This is relatively easy: just update http://autobuild.buildroot.org/branches
with new branches and new ratios.

Regards,
Yann E. MORIN.

>  Regards,
>  Arnout
> 
> > 
> > 
> >>  > Should I go ahead and make the change ?
> >>
> >> It sounds sensible to me, yes.
> > 
> >  +1
> > 
> >  Regards,
> >  Arnout
> > 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-08-21  7:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190819054333.566812D8079@tinkie.tkos.co.il>
2019-08-19 12:49 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18 Baruch Siach
2019-08-19 12:55   ` Thomas Petazzoni
2019-08-19 21:28     ` Arnout Vandecappelle
2019-08-19 21:32       ` Thomas Petazzoni
2019-08-19 22:00         ` Peter Korsgaard
2019-08-20 19:10           ` Arnout Vandecappelle
2019-08-20 19:18             ` Arnout Vandecappelle
2019-08-21  7:51               ` Yann E. MORIN [this message]
2019-08-21  8:01                 ` Peter Korsgaard
2019-08-21  9:13                   ` Yann E. MORIN
2019-08-21 10:03                     ` Peter Korsgaard
2019-08-21 20:58                       ` Arnout Vandecappelle
2019-08-26  7:38                       ` Thomas Petazzoni
2019-08-27 20:17                         ` Peter Korsgaard
2019-08-28 12:37   ` Thomas Petazzoni
     [not found] <5d5a3ea8.1c69fb81.80346.bed9SMTPIN_ADDED_MISSING@mx.google.com>
     [not found] ` <CAFtSRGAfbahUOhw2FEZ5mD1F0s3NpN1kmW5PxkHmPr83yhrxyg@mail.gmail.com>
2019-08-19 12:03   ` Thomas Petazzoni

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=20190821075136.GA12477@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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