Re: [Buildroot] [PATCH next 1/1] package/kexec: fix link error when BR2_OPTIMIZE_0=y

[Julien Olivain <ju.o@free.fr>]

Hi Thomas,

On 22/08/2023 22:35, Thomas Petazzoni wrote:
> On Tue, 22 Aug 2023 22:08:32 +0200
> Julien Olivain <ju.o@free.fr> wrote:
> 
>> This could indeed go into the master branch. Since 2023.08-rc2 was
>> already tagged, I imagined only major fixes would go into master.
>> This one has been longstanding issue (so apparently not so important).
>> 
>> In fact, reading the Buildroot documentation release engineering at 
>> [1]
>> does really allow me to decide what kind of commits (security, 
>> bugfixes,
>> new features, minor improvements like typos) should go to master/next.
>> 
>> Recently, I had the same interpretation in [2] that a minor 
>> improvement
>> (in which nothing was actually broken) should go to next. Yann 
>> preferred
>> master.
>> 
>> If you summarize those situations, I would be happy to propose a doc
>> improvement.
> 
> Essentially, the idea after -rc1 is to stop applying version bumps and
> major changes in master so that master progressively converges to
> something "stable" that we can release. So, we can still merge
> improvements and fixes to master. As such, the build fix for kexec
> definitely qualifies. The license file improvement for lsof that you
> pointed also qualifies: it's an improvement, very low risk. Of course,
> there's always a grey area, even for version bumps: sometimes we take a
> version bump in master because it fixes security issues. Sometimes we
> prefer to backport the patch fixing the security issue rather than
> bumping when the number of other changes that take place with the
> version bump is too large.
> 
> Does that help? :-)

Yes it does!  From now on, I'll also include minor improvements and 
bugfixes
to master. Thanks for the clarification.

> 
> Thomas

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot