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 11:13:36 +0200	[thread overview]
Message-ID: <20190821091336.GD12477@scaer> (raw)
In-Reply-To: <87v9ur54mx.fsf@dell.be.48ers.dk>

Peter, All,

On 2019-08-21 10:01 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>  >> 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,

Well, usual version control best practices suggests the opposite: all
fixes are done on master, and when relevant, back-ported to the stable
branch(es).

This is no different than what you do today when you backport changes
from master to the stable branches, except it happens right from -rc1
instead of after the final release. It is the exact same process.

> and website changes needs to happen on master
> rather than stable.

But that's already the case, no?

> 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 ;)

Yeah, I know habbits, as bad as they might be, are hard to break! ;-p

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

How would that be different from today? I would say that today, for each
release cycle, there are two changes:

  - one to introduce next in the list (after -rc1)
  - one to introduce the new stable rbanch and remove next and the
    oldest stable branch (after the release)

with the proposed change, there would be a single change per release:

  - one to add the new stable branch and remove the oldest stable branch
    (after -rc1)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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  9:13 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 [this message]
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=20190821091336.GD12477@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