public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Subject: bitbake 2 is outdated
Date: Fri, 10 Feb 2023 20:35:00 +0100	[thread overview]
Message-ID: <20230210203500.524a4669@md1za8fc.ad001.siemens.net> (raw)

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

             reply	other threads:[~2023-02-10 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 19:35 Henning Schild [this message]
2023-02-10 19:40 ` Anton Mikanovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230210203500.524a4669@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox