bitbake 2 is outdated

bitbake 2 is outdated

[Henning Schild]

Hi all,

i think we are now at bitbake 2.0.5

a9bbdeeb7174 ("bitbake: update to Bitbake 2.0.5")

upstream is at 2.2

the "small jump" in Isar might have been intentional to split up the
"major" and "what is to come"

But now that this is done we can/should? look into going from 2.0.5 to
2.2.

In the hope that we get fixes and not even more interface changes.

I did not follow why we decided to small jump, it likely makes sense.
But we should try to catch up and not leave fixes behind now, looking
at upstream bitbake code for my latest layer migration ... i kind of
had the feeling we have bugs worth fixing. But no blocking points at
the moment.

Just a strong feeling that we should keep up to get fixes and detect
new lurking problems early ... because we have to follow anyhow.

Henning

Re: bitbake 2 is outdated

[Anton Mikanovich]

10/02/2023 21:35, Henning Schild wrote:
> Hi all,
>
> i think we are now at bitbake 2.0.5
>
> a9bbdeeb7174 ("bitbake: update to Bitbake 2.0.5")
>
> upstream is at 2.2
>
> the "small jump" in Isar might have been intentional to split up the
> "major" and "what is to come"
>
> But now that this is done we can/should? look into going from 2.0.5 to
> 2.2.
>
> In the hope that we get fixes and not even more interface changes.
>
> I did not follow why we decided to small jump, it likely makes sense.
> But we should try to catch up and not leave fixes behind now, looking
> at upstream bitbake code for my latest layer migration ... i kind of
> had the feeling we have bugs worth fixing. But no blocking points at
> the moment.
>
> Just a strong feeling that we should keep up to get fixes and detect
> new lurking problems early ... because we have to follow anyhow.
>
> Henning
>
Bitbake 2.0 is used in LTS branch of Yocto 4.0, while 2.2 is used in 4.1
supported until May 2023 only. That's why we've switched to 2.0.5 only 
for now.