From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ben Brenson <benbrenson89@googlemail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Isar fork
Date: Wed, 18 Oct 2017 14:09:16 +0200 [thread overview]
Message-ID: <c5e2fcde-f539-6564-4513-e736d1e6186e@siemens.com> (raw)
In-Reply-To: <c252443b-29ca-4a27-a7a5-f329a87533b3@googlegroups.com>
On 2017-10-18 13:56, 'Ben Brenson' via isar-users wrote:
> Hi Jan,
> yes you are right, the baseline of the isar fork is quiet old.
> We had to implement some features quiet fast to get a first image build
> working.
> Combined with the open source agreement, we forked this repository and
> started developing.
>
> Since a lot of the codebase has changed, related to 25 May, a little bit
> of effort is required to work out some patches, but I will try do handle
> this.
> The first feature I intent to post, would be the chroot related stuff,
> because the most changes are related to the bitbake core itself, which
> should be at the same state as
> my repository.
>
> So adding this feature won't force Isar to make use of them, but the
> possibility of using them may be available after.
> So I think I will start with that feature, by submitting patch series.
Yes, start with the simplest, best isolated feature first. That will
help get the ball rolling.
>
> The other features will dive very deep into isar, and the codebase
> differs a lot now.
> This fact never offered the possibility of frequently rebasing against
> upstream.
> So rebasing now against the main repository will be a time consuming
> job, but is required :-(
I fully understand, and something similar happened to us before. If
project pressure comes in, you can easily be forced off-track and then
have to pay the price later on.
However, it would have been valuable to participate in the requirement
discussions early. That might have enabled us to prioritize features and
sharpening their scope to address your needs as well.
>
> May be rebasing the current Isar features against my repo will be much
> easier to handle,
> but doesn't that miss the goal of getting my features mainlined into
> current mainline Isar?
Indeed. Upstream is Isar, not a specific fork of it. By now, we are
working on a number of products that build upon upstream Isar, are
mostly happy, but will surely further improve the core to improve the
usability. Eventually, you will miss those features in your fork, I'm sure.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-10-18 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 9:23 Ben Brenson
2017-10-18 11:16 ` Jan Kiszka
2017-10-18 11:56 ` Ben Brenson
2017-10-18 12:09 ` Jan Kiszka [this message]
2017-10-18 11:56 ` Claudius Heine
2017-10-18 12:11 ` Ben Brenson
2017-10-18 12:52 ` Claudius Heine
2017-10-18 14:02 ` Ben Brenson
2017-10-18 14:19 ` Henning Schild
2017-10-18 14:22 ` Claudius Heine
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=c5e2fcde-f539-6564-4513-e736d1e6186e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=benbrenson89@googlemail.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