From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [ANNOUNCE] Upcoming ISAR release
Date: Mon, 18 Feb 2019 11:25:04 +0100 [thread overview]
Message-ID: <94924dd9-ae84-4e10-655f-a4afa86842a7@siemens.com> (raw)
In-Reply-To: <b928b55f-4826-14c5-adc8-0d70646b2b4a@ilbers.de>
On 18.02.19 10:01, Maxim Yu. Osipov wrote:
> Hello everybody,
>
> Last release (v0.6) was made on 1st of October 2018.
>
> We plan to release the next version of ISAR on 1st of March, 2019.
>
> BTW, what do you think about making a 1.0 release?
At least reproducible build should be solved for that. I think we have currently
three open issues in that area:
- switching between cached and non-cached builds on the fly
- cache unconditionally (make related task implicit)
- cache source package (re-)builds
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-18 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:01 Maxim Yu. Osipov
2019-02-18 9:58 ` Claudius Heine
2019-02-18 10:29 ` Maxim Yu. Osipov
2019-02-18 11:52 ` Claudius Heine
2019-02-18 17:16 ` Henning Schild
2019-02-18 20:09 ` Jan Kiszka
2019-02-18 10:07 ` Henning Schild
2019-02-18 10:25 ` Jan Kiszka [this message]
2019-02-26 14:23 ` cedric_hombourger
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=94924dd9-ae84-4e10-655f-a4afa86842a7@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