From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [ANNOUNCE] Upcoming ISAR release
Date: Mon, 18 Feb 2019 11:07:29 +0100 [thread overview]
Message-ID: <20190218110729.3373a58e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <b928b55f-4826-14c5-adc8-0d70646b2b4a@ilbers.de>
Am Mon, 18 Feb 2019 10:01:09 +0100
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> 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?
A 1.0 is a good idea, but my personal feeling is that we are not there
yet. There are still a lot of minor issues and at the same time we are
gaining important features.
Henning
> At the moment I'm busy with testing/applying pending patches, I plan
> to finish this activity in a couple of days and make a first release
> candidate and code freeze (only bug fixes will be applied in the
> 'next') after that.
>
> I'll submit later Changelog describing major changes since the last
> release and sort out the issues present on the project's wiki.
>
> Please inform me about any open issues that may be a subject to
> postpone a release.
>
> Thanks,
> Maxim.
next prev parent reply other threads:[~2019-02-18 10:07 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 [this message]
2019-02-18 10:25 ` Jan Kiszka
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=20190218110729.3373a58e@md1za8fc.ad001.siemens.net \
--to=henning.schild@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