From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Next release?
Date: Mon, 20 Aug 2018 08:51:32 +0200 [thread overview]
Message-ID: <afc4a2c0-346f-aedf-8de4-43c5ef8b605d@siemens.com> (raw)
In-Reply-To: <352f239a-a281-d023-2e99-bbfedbab17f2@ilbers.de>
On 2018-08-20 08:50, Maxim Yu. Osipov wrote:
> Hi Jan,
>
> I agree with you.
> I plan to add to the release compatibility matrix
> (and to test it) which lists supported
> architectures/releases/features:
>
> Something like that:
>
> debian jessie arm native yes
> debian jessie arm cross no
> debian jessie arm sdk ?
>
> Any ideas/suggestions how to name this file?
Unless that become a huge table, why not simple create a section in the
README?
Jan
>
> Regards,
> Maxim.
>
> On 08/20/2018 09:24 AM, Jan Kiszka wrote:
>> Hi all,
>>
>> quite a few useful features went in recently. The next big one should
>> be reproducibility, but I feel like a release would do well before
>> that. Any plans?
>>
>> Jan
>>
>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-08-20 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 6:24 Jan Kiszka
2018-08-20 6:50 ` Maxim Yu. Osipov
2018-08-20 6:51 ` Jan Kiszka [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=afc4a2c0-346f-aedf-8de4-43c5ef8b605d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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