From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire Core 135 testing
Date: Fri, 30 Aug 2019 14:31:29 +0100 [thread overview]
Message-ID: <ECF66D53-69E9-40FE-909A-9CBBA48689D6@ipfire.org> (raw)
In-Reply-To: <H000006e0051eec0.1567017214.mail.at4b.net@MHS>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hello,
Thank you for the feedback.
I have also tested a fresh installation which looked fine to me.
I will consult with Arne for a release date I suppose early next week.
If anyone has anything, please raise your hand now!
Best,
-Michael
> On 28 Aug 2019, at 19:33, Kienker, Fred <fkienker(a)at4b.com> wrote:
>
> Just reporting - we have been through our testing cycle for Core 135 and have found no issues to report. We have seen better stability in unbound in C135, for reasons unknown, compared to C134.
>
> Eagerly anticipating the official release.
> Best regards,
> Fred Kienker
next parent reply other threads:[~2019-08-30 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <H000006e0051eec0.1567017214.mail.at4b.net@MHS>
2019-08-30 13:31 ` Michael Tremer [this message]
2019-08-30 17:41 ` peter.mueller
2019-08-30 22:35 ` Kienker, Fred
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=ECF66D53-69E9-40FE-909A-9CBBA48689D6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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