Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Rich Brown <richb.hanover@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] notes on going for a stable release
Date: Wed, 15 Jan 2014 22:20:29 -0500	[thread overview]
Message-ID: <20140116032029.GA14736@thunk.org> (raw)
In-Reply-To: <EFE76702-EC41-4379-8DE8-4DEF8FD8AC91@gmail.com>

On Tue, Jan 14, 2014 at 08:20:12AM -0500, Rich Brown wrote:
> Since I kicked off this thread, let me second what David and Toke have said.
> 
> I used the wrong word - "stable" - when I really wanted a new stake
> in the ground. Our first was CeroWrt 3.7.5-2 - it was great. I used
> it for a long time before these newer builds got even better and I
> was willing to risk family ire. (So far, so good with 3.10.24-8).

As I suggested earlier, what would be useful is making the distinction
between "unstable" and "testing".  On an internal misc- mailing list
at my company, the topic of more secure/reliable wireless AP's came
up, and I recommended Cerowrt.  The response I got back was, roughly
paraphrased, "I was looking on the mailing list, and it seems that
every couple of releases there's some catastrophic breakage; it's too
exciting for me".

Without actually suggesting a commitment of two years worth of
security bug fixes, just something of the form, "our dedicated
unstable testers have been using it for the last week, and it it's
probably not likely to eat your children" (well, your children's web
sites, anyway).

						- Ted

  parent reply	other threads:[~2014-01-16  3:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  6:07 Dave Taht
2014-01-14  8:37 ` Christopher Robin
2014-01-14  9:44   ` Toke Høiland-Jørgensen
2014-01-14 12:51     ` David Personette
2014-01-14 13:20       ` Rich Brown
2014-01-14 15:30         ` Dave Taht
2014-01-16  3:20         ` Theodore Ts'o [this message]
2014-01-15 15:18   ` Dave Taht
2014-01-14 12:10 ` Juergen Botz
2014-01-14 15:10   ` Dave Taht
2014-01-14 12:36 ` David Personette
2014-01-15  4:11   ` Dave Taht
     [not found]     ` <CAMybZqzs9ES9G23ke-PjU759wxbQNMytYa4EHmv0H8HqpPwwPQ@mail.gmail.com>
2014-01-15 14:47       ` Dave Taht
2014-01-15  0:30 ` David Lang
2014-01-15 17:31 ` Jim Reisert AD1C
2014-01-20 15:00 ` Maciej Soltysiak
2014-01-20 15:15   ` [Cerowrt-devel] notes on going for a stable release/replacement router Rich Brown

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140116032029.GA14736@thunk.org \
    --to=tytso@mit.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    --cc=toke@toke.dk \
    /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