[PATCH] docs: set_versions.py: update current releases

[PATCH] docs: set_versions.py: update current releases

[Antonin Godard]

Remove dunfell, nanbield, add styhead as active release.
Remove dunfell from ltsseries.

The switcher menu now contains:

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
@Quentin, I'd appreciate your review as I see you modified this file in
the past. From what I've seen locally, the Styhead release does not show
up in the switchers. Is that something that is done automagically by
the autobuilder?
---
 documentation/set_versions.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/set_versions.py b/documentation/set_versions.py
index dec078083441263cb1350532b2749f5ee222d555..77fcedef7c28165704b79ab8d506a466110b8249 100755
--- a/documentation/set_versions.py
+++ b/documentation/set_versions.py
@@ -26,9 +26,9 @@ ourversion = None
 if len(sys.argv) == 2:
     ourversion = sys.argv[1]
 
-activereleases = ["scarthgap", "nanbield", "kirkstone", "dunfell"]
+activereleases = ["styhead", "scarthgap", "kirkstone"]
 devbranch = "styhead"
-ltsseries = ["scarthgap", "kirkstone", "dunfell"]
+ltsseries = ["scarthgap", "kirkstone"]
 
 # used by run-docs-builds to get the default page
 if ourversion == "getlatest":

---
base-commit: afeded9939777d88bf4cb9ebf7a61aadd476642d
change-id: 20241025-update-switchers-6d72cd2aadb6

Best regards,
-- 
Antonin Godard <antonin.godard@bootlin.com>

Re: [PATCH] docs: set_versions.py: update current releases

[Quentin Schulz]

Hi Antonin,

On 10/25/24 2:00 PM, Antonin Godard wrote:
> Remove dunfell, nanbield, add styhead as active release.
> Remove dunfell from ltsseries.
> 
> The switcher menu now contains:
> 

The suspense is killing me!

> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> @Quentin, I'd appreciate your review as I see you modified this file in
> the past. From what I've seen locally, the Styhead release does not show
> up in the switchers. Is that something that is done automagically by
> the autobuilder?

I've barely touched the autobuilder so no clue what it's supposed to do.

But we anyway need to do some manual updates as there's no way we can 
know the release number mapped to a release name. Similarly for the 
mapping between the release number of OE/YP and bitbake.

And finally, how do we know which release is still supported or not and 
which ones are LTSes?

> ---
>   documentation/set_versions.py | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/documentation/set_versions.py b/documentation/set_versions.py
> index dec078083441263cb1350532b2749f5ee222d555..77fcedef7c28165704b79ab8d506a466110b8249 100755
> --- a/documentation/set_versions.py
> +++ b/documentation/set_versions.py
> @@ -26,9 +26,9 @@ ourversion = None
>   if len(sys.argv) == 2:
>       ourversion = sys.argv[1]
>   
> -activereleases = ["scarthgap", "nanbield", "kirkstone", "dunfell"]
> +activereleases = ["styhead", "scarthgap", "kirkstone"]
>   devbranch = "styhead"
> -ltsseries = ["scarthgap", "kirkstone", "dunfell"]
> +ltsseries = ["scarthgap", "kirkstone"]
>   

This looks fine, albeit incomplete maybe?

We should probably also get ready for Walnascar.

https://wiki.yoctoproject.org/wiki/Releases says Walnascar will be 5.2 
with bitbake 2.12.

So I assume we can do the following:

-devbranch = "styhead"
+devbranch = "walnascar"

+release_series["walnascar"] = "5.2"

+    "walnascar" : "2.12",

Similarly to what was done in cfbb2cda2c3d221f944ae610c05039c9d12093bc

I remember not having a lot of fun in this python script. We should 
probably document the code much better and see if there's something we 
could do to improve readability.

I remember we have some bugs open for the docs that shows some version 
number for dev it shouldn't be or something.

Hope this helps.

Cheers,
Quentin

Re: [PATCH] docs: set_versions.py: update current releases

[Antonin Godard]

Hi Quentin,

On Fri Oct 25, 2024 at 3:01 PM CEST, Quentin Schulz wrote:
> Hi Antonin,
>
> On 10/25/24 2:00 PM, Antonin Godard wrote:
>> Remove dunfell, nanbield, add styhead as active release.
>> Remove dunfell from ltsseries.
>>
>> The switcher menu now contains:
>>
>
> The suspense is killing me!

Oops!

>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> @Quentin, I'd appreciate your review as I see you modified this file in
>> the past. From what I've seen locally, the Styhead release does not show
>> up in the switchers. Is that something that is done automagically by
>> the autobuilder?
>
> I've barely touched the autobuilder so no clue what it's supposed to do.
>
> But we anyway need to do some manual updates as there's no way we can
> know the release number mapped to a release name. Similarly for the
> mapping between the release number of OE/YP and bitbake.
>
> And finally, how do we know which release is still supported or not and
> which ones are LTSes?

Yep, that's also what I figured…

>> ---
>>   documentation/set_versions.py | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/documentation/set_versions.py b/documentation/set_versions.py
>> index dec078083441263cb1350532b2749f5ee222d555..77fcedef7c28165704b79ab8d506a466110b8249 100755
>> --- a/documentation/set_versions.py
>> +++ b/documentation/set_versions.py
>> @@ -26,9 +26,9 @@ ourversion = None
>>   if len(sys.argv) == 2:
>>       ourversion = sys.argv[1]
>>
>> -activereleases = ["scarthgap", "nanbield", "kirkstone", "dunfell"]
>> +activereleases = ["styhead", "scarthgap", "kirkstone"]
>>   devbranch = "styhead"
>> -ltsseries = ["scarthgap", "kirkstone", "dunfell"]
>> +ltsseries = ["scarthgap", "kirkstone"]
>>
>
> This looks fine, albeit incomplete maybe?
>
> We should probably also get ready for Walnascar.

Probably, yes, although I'm not sure what the implications are since there are
not tags/branch created for this release, which is why I wanted to do styhead
first since it's out.

> https://wiki.yoctoproject.org/wiki/Releases says Walnascar will be 5.2
> with bitbake 2.12.
>
> So I assume we can do the following:
>
> -devbranch = "styhead"
> +devbranch = "walnascar"
>
> +release_series["walnascar"] = "5.2"
>
> +    "walnascar" : "2.12",
>
> Similarly to what was done in cfbb2cda2c3d221f944ae610c05039c9d12093bc

I'll try again and modify the poky.yaml.in and others, see how all of that
works.

> I remember not having a lot of fun in this python script. We should
> probably document the code much better and see if there's something we
> could do to improve readability.

Yeah, seems a bit all over the place. I'll try to understand it, see how it can
be improved.

> I remember we have some bugs open for the docs that shows some version
> number for dev it shouldn't be or something.

I'll have a look. Thanks for your insights!

Cheers,
Antonin

--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com