Re: [PATCH v2 17/17] Documentation: migration-2025.11.0: List changes to CONFIG_CRYPTO_PUBLIC_KEYS

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

Hi,

On 11/3/25 11:41 AM, Sascha Hauer wrote:
> On Mon, Nov 03, 2025 at 11:26:34AM +0100, Ahmad Fatoum wrote:
>>
>>
>> On 11/3/25 11:16 AM, Sascha Hauer wrote:
>>> On Tue, Oct 28, 2025 at 07:03:22PM +0100, Jonas Rebmann wrote:
>>>> As part of the introduction of TLV signature in public key keyrings,
>>>> there is a new interpreter for CONFIG_CRYPTO_PUBLIC_KEYS in
>>>> scripts/keytoc.c. All users should update to the new syntax and are
>>>> presented with a warning. Users with invalid characters in the legacy
>>>> syntax must change the fit-hint and will be presented with an error.
>>>>
>>>> Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
>>>> ---
>>>>  Documentation/migration-guides/migration-2025.11.0.rst | 15 +++++++++++++++
>>>>  1 file changed, 15 insertions(+)
>>>>
>>>> diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst
>>>> index a9c7abb66e..bd7fcf8126 100644
>>>> --- a/Documentation/migration-guides/migration-2025.11.0.rst
>>>> +++ b/Documentation/migration-guides/migration-2025.11.0.rst
>>>
>>> migration-2025.12.0.rst please.
>>
>> Should we rethink the scheme to avoid this in future?
> 
> Yes. The contributor shouldn't need to know which release a series
> targets and also not have to remember to move it to another migration
> guide when sending a new revision after a release.
> 
>>
>> Two suggestions come to mind:
>>
>> - We add migration-next.rst and migration-master.rst files, where stuff
>> can be added and then they are renamed before release:
>>
>> migration-master.rst -> migration-${version}.rst
>> migration-next.rst -> migration-master.rst
>> <empty file> -> migration-next.rst
> 
> No need to split this up into migration-master.rst and
> migration-next.rst. Let's just use migration.rst. I'll rename
> that to migration-20xx.yy right before a release.

I would still call it migration-upcoming.rst or migration-next.rst for
clarity. One file sounds workable.

Cheers,
Ahmad

> 
> Sascha
> 

-- 
Pengutronix e.K.                  |                             |
Steuerwalder Str. 21              | http://www.pengutronix.de/  |
31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |