public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2
Date: Sat, 16 Jul 2016 08:59:29 +0200	[thread overview]
Message-ID: <18c17912-7632-71a7-ddde-71f38f473dd3@ipfire.org> (raw)
In-Reply-To: <CACOO0z8ZGnBa2rCKEqU+4dgiVWb0ZjZHvpbd3fgv-KvDK524zg@mail.gmail.com>

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

Hi,

Ok, next.

Am I right assuming that the '2.0-002'-version at
http://people.ipfire.org/~stevee/guardian-2.0/ plus
http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/ is
the latest!?

Best,
Matthias

On 16.07.2016 04:03, Mark Coolen wrote:
> I'm willing to test it as well. I take it the instructions from
> http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire are still
> good?
> 
> On Fri, Jul 15, 2016 at 8:23 PM, R. W. Rodolico <rodo(a)dailydata.net> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Tell me what I need to do to test Guardian. I've never installed it,
>> but I am doing it now.
>>
>> Rod
>>
>> On 07/15/2016 05:00 AM, Michael Tremer wrote:
>> > 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
>>
>> - --
>> Rod Rodolico
>> Daily Data, Inc.
>> POB 140465
>> Dallas TX 75214-0465
>> 214.827.2170
>> http://www.dailydata.net
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>>
>> iEYEARECAAYFAleJfncACgkQuVY3UpYMlTQ1ywCfdXuAC8ByMYEOKBpkvV0R+BRm
>> hhAAnR9juXlTjDlTiFMPbGOpDAP9LkOG
>> =5XbU
>> -----END PGP SIGNATURE-----
>>
> 
> 
> 


       reply	other threads:[~2016-07-16  6:59 UTC|newest]

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