[Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18

Yann E. MORIN yann.morin.1998 at free.fr
Wed Aug 21 09:13:36 UTC 2019


Peter, All,

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



More information about the buildroot mailing list