Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18
Date: Wed, 21 Aug 2019 10:01:10 +0200	[thread overview]
Message-ID: <87v9ur54mx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190821075136.GA12477@scaer> (Yann E. MORIN's message of "Wed,  21 Aug 2019 09:51:36 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 >> 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.

We could do that as well. We then need to merge in the other direction
(stable->master) to ensure fixes after rc1 (and updates to the CHANGES
file) are not dropped, and website changes needs to happen on master
rather than stable.

It seems a bit more complicated to me, but that might just be because I
have done the other way around for 10+ years by now ;)


 >> 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.

Yes, but this file in manually maintained and only accessible by Thomas,
right?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-08-21  8:01 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 [this message]
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=87v9ur54mx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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