From: Anton Mikanovich <amikan@ilbers.de>
To: Baurzhan Ismagulov <ibr@ilbers.de>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v5 00/21] Migrate to Bitbake 2.0
Date: Mon, 5 Dec 2022 15:31:13 +0300 [thread overview]
Message-ID: <6feb9f47-5809-0860-a37b-ee567aaadd32@ilbers.de> (raw)
In-Reply-To: <68c793636161a898e110b28dba3a91702a8cc40f.camel@siemens.com>
05.12.2022 14:52, Moessbauer, Felix wrote:
> Hi,
>
> would it be possible to create an ISAR release before we eventually
> integrate bitbake 2.0? We currently have a lot of layers which already
> moved to master or even next and by that face constant change.
> Others are still stuck at 0.9 without sbuild and sstate-cache.
>
> Bringing these layers back to a release point would significantly
> reduce the maintenance effort.
>
> Felix
Hello Felix,
Originally we've planned to make a release after integrating both sbuild and
bitbake, this is what we came to previously. But we are not against creating
another release in between as a milestone if needed.
prev parent reply other threads:[~2022-12-05 12:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:36 Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 01/21] meta: change deprecated parse calls Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 02/21] scripts/contrib: Add override conversion script Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 03/21] scripts/contrib: configure " Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 04/21] meta-isar: set default branch names Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 05/21] meta: remove non recommended syntax Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 06/21] bitbake: Update to Bitbake 2.0.5 Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 07/21] doc: require zstd tool Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 08/21] meta: update bitbake variables Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 09/21] bitbake.conf: align hash vars with openembedded Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 10/21] meta: mark network and sudo tasks Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 11/21] meta: update overrides syntax Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 12/21] sstate: update bbclass Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 13/21] bitbake.conf: declare default XZ and ZSTD options Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 14/21] Revert "devshell: Use different termination test to avoid warnings" Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 15/21] meta: align with OE-core libraries update Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 16/21] Revert "Revert "devshell: Use different termination test to avoid warnings"" Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 17/21] CI: Adopt tests to syntax change Anton Mikanovich
2022-12-02 14:36 ` [PATCH v5 18/21] isar-sstate: adopt sstate maintenance script Anton Mikanovich
2022-12-03 4:57 ` Moessbauer, Felix
2022-12-03 5:29 ` Schmidt, Adriaan
2022-12-06 8:57 ` Anton Mikanovich
2022-12-06 9:36 ` Moessbauer, Felix
2022-12-02 14:36 ` [PATCH v5 19/21] RECIPE-API-CHANGELOG: Add tips after bitbake version update Anton Mikanovich
2022-12-02 14:37 ` [PATCH v5 20/21] Revert "bitbake: Make 3.6.0 the minimum python version" Anton Mikanovich
2022-12-02 14:37 ` [PATCH v5 21/21] Revert "utils/ply: Change md5 usages to work on FIPS enabled hosts" Anton Mikanovich
2022-12-02 14:45 ` [PATCH v5 00/21] Migrate to Bitbake 2.0 Anton Mikanovich
2022-12-05 11:34 ` Florian Bezdeka
2022-12-05 11:57 ` Anton Mikanovich
2022-12-05 11:52 ` Moessbauer, Felix
2022-12-05 12:31 ` Anton Mikanovich [this message]
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=6feb9f47-5809-0860-a37b-ee567aaadd32@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--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