public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Lightning talk about ISAR
Date: Fri, 10 Dec 2021 12:23:32 +0100	[thread overview]
Message-ID: <2dc10075-143d-0114-1163-9a9d9075d9b1@siemens.com> (raw)
In-Reply-To: <20211210105632.GK22100@yssyq.m.ilbers.de>

On 10.12.21 11:56, Baurzhan Ismagulov wrote:
> On Thu, Dec 09, 2021 at 11:02:01PM +0100, Henning Schild wrote:
>> the talk went well and i think we can conclude that Isar adoption is
>> right on track! We have many stakeholders building their firmwares with
>> Isar and being pretty happy with it!
> 
> Glad to hear that!
> 
> 
>> We did have a poll at the end to see where users see room for
>> improvement. I hope Felix will share the results ... but the number one
>> topic was "documentation" if i recall correctly.
> 
> Yes, I agree it's time to prioritize this continuous TODO item. If you have a
> list of specific topics other than known ones, it would help.
> 
> 
>> Surpringly the API
>> changelog seems fine ... even if we have to break things every once i a
>> while!
> 
> This is also good to know.
> 
> 
> On Fri, Nov 26, 2021 at 09:20:48PM +0100, Henning Schild wrote:
>> i stopped all rebasing and pinging because we need that sstate to speed
>> up and get all those open MRs merged. Some of them introduce tests and
>> i decided to hold them back after avocado. Will be happy to re-send
>> once sstate is in and we gain some much needed speed.
> 
> Now that avocado and sstate cache is in, if any other patches have priority,
> please give us a hint.
> 

IMHO: Stabilization patches so that 0.8-rc1 can be tagged and then 0.8.
After that, we should look into sbuild and other refactorings that are
pending.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2021-12-10 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 10:42 Moessbauer, Felix
2021-11-25 16:26 ` Jan Kiszka
2021-11-25 20:17 ` Henning Schild
2021-11-26 20:20   ` Henning Schild
2021-12-09 22:02 ` Henning Schild
2021-12-10 10:56   ` Baurzhan Ismagulov
2021-12-10 11:06     ` Moessbauer, Felix
2021-12-10 11:23     ` Jan Kiszka [this message]
2021-12-10 11:36       ` Baurzhan Ismagulov
2021-12-13 21:17         ` Henning Schild
2021-12-15  8:49           ` Baurzhan Ismagulov
2021-12-14 13:15         ` Schmidt, Adriaan

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=2dc10075-143d-0114-1163-9a9d9075d9b1@siemens.com \
    --to=jan.kiszka@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