public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"ibr@radix50.net" <ibr@radix50.net>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH(sbuild) 1/1] sbuild: Add changelog entry
Date: Wed, 18 May 2022 16:10:25 +0000	[thread overview]
Message-ID: <f299e0b02aa6e0d9a41d66d101c15f3fcafa3e58.camel@siemens.com> (raw)
In-Reply-To: <YoUYw3MK9LAajJgC@ilbers.de>

On Wed, 2022-05-18 at 18:03 +0200, Baurzhan Ismagulov wrote:
> On Wed, May 18, 2022 at 03:54:34PM +0000, Bezdeka, Florian wrote:
> > Uh... Wait... Is that sbuild stuff already merged? 
> > 
> > I'm expecting quite some trouble in downstream layers when trying to
> > update ISAR next time. I would vote for the following to avoid a
> > "migrate all at once" scenario:
> > 
> > - Apply all pending patches (except sbuild stuff)
> > - Prepare a new "stable release 0.9" and maintain that "branch" for
> >   some time. 
> > - branch out for ISAR 1.0, apply sbuild stuff there
> > 
> > That would allow downstream layers to test and migrate in multiple
> > iterations against the 1.0 release. I guess sbuild will discover some
> > build problems. If layers have more such problems updating all at once
> > can be hard.
> 
> The sbuild series has not been merged yet. We are thinking how to handle this
> and will continue the discussion.
> 
> In short, "all pending patches" is quite a moving target, there will always be
> patches that are important. That said, many of the recently requested ones have
> been merged. Maintaining a stable version for some time is not an easy decision
> due to the effort and has to be carefully considered.

Adding back some CCs so colleagues are notified as well. At least I'm
interested in this discussion.

> 
> With kind regards,
> Baurzhan.
> 


  reply	other threads:[~2022-05-18 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 15:12 Anton Mikanovich
2022-05-18 15:54 ` Bezdeka, Florian
2022-05-18 16:03   ` Baurzhan Ismagulov
2022-05-18 16:10     ` Bezdeka, Florian [this message]
2022-05-27  8:21       ` Baurzhan Ismagulov
2022-05-18 16:54   ` Henning Schild

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=f299e0b02aa6e0d9a41d66d101c15f3fcafa3e58.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=ibr@radix50.net \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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