From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18
Date: Mon, 26 Aug 2019 09:38:59 +0200 [thread overview]
Message-ID: <20190826093859.1ceee67d@windsurf.home> (raw)
In-Reply-To: <87r25e6dj1.fsf@dell.be.48ers.dk>
Hello,
On Wed, 21 Aug 2019 12:03:46 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> > - one to add the new stable branch and remove the oldest stable branch
> > (after -rc1)
>
> But that doesn't take the weights into consideration, so we would end up
> spending most of the autobuilder time on master (E.G. what we now call
> next).
>
> Anyway, I am OK with giving it a try for 2019.11, but I'm not completely
> convinced about it.
I also don't really see the benefit(s) of this change. To me, it seems
a lot easier to just adjust the logic that generates the package
statistics to use the next branch when it is available. The rest of our
existing workflow can continue to work as-is. It's already confusing
for some of our contributors, if in addition to that we keep changing
our workflow for gratuitous reasons, it is not going to help.
So I'm not really in favor of changing the workflow, unless there is
some clear benefit to it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-26 7:38 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
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 [this message]
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=20190826093859.1ceee67d@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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