public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2
Date: Fri, 15 Jul 2016 11:00:20 +0100	[thread overview]
Message-ID: <1468576820.2710.125.camel@ipfire.org> (raw)
In-Reply-To: <5787875A.2000600@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

Hi guys,

even if you have a conversation on the phone, please try keeping us in the loop.

So the key points of what I know:

* A release is targeted for core update 104

* There are a few changes required so that re-blocking a host after it has been
manually unblocked allows this host the configured number of tries again and not
only one.

* Many more testers are required since feedback is really low at this point.

Did I get this right? What is the ETA for a set of patches on the mailing list?

What is the plan to engage more testers?

Best,
-Michael

On Thu, 2016-07-14 at 14:36 +0200, Daniel Weismüller wrote:
> Hi Stevee
> I know you are very busy and working hard on the this.
> But if you want to release the new Guardian 2 with Core 104 we still 
> need to do some work and it must be tested!
> So please tell us something about the new guardian2 and the state of 
> your work.
> 
> Maybe we find more testers here on the list.
> 
> Meanwhile I've talked with Michael about the state which I know of the 
> guardian2 and we both go confirm that the list of blocked IPs which runs 
> in the background isn't a good idea.
> Please let us talk by phone about it again.
> 
> -
> Daniel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-15 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 12:36 Daniel Weismüller
2016-07-15 10:00 ` Michael Tremer [this message]
2016-07-16  0:23   ` R. W. Rodolico
     [not found] <CACOO0z8ZGnBa2rCKEqU+4dgiVWb0ZjZHvpbd3fgv-KvDK524zg@mail.gmail.com>
2016-07-16  6:59 ` Matthias Fischer
     [not found] <CACOO0z-ZmvxauaLjrv5nLX_kctaPcbMB1nGNZy02iT=E5FDNEA@mail.gmail.com>
2016-07-16 15:12 ` Matthias Fischer
2016-07-16 18:43 ` R. W. Rodolico
     [not found] <CACOO0z9xQoJh8PY74M4pdxRe8TOATF_SwjM65FtbDMexXq6mOA@mail.gmail.com>
2016-07-18  4:37 ` R. W. Rodolico
     [not found] <CACOO0z_FEq0DmoAqrH=hjyTNo8rpgpUt-obJ2nFDabhU4-NVyg@mail.gmail.com>
2016-07-19  4:25 ` R. W. Rodolico

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=1468576820.2710.125.camel@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