Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Richard E. Brown" <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Aaron Wood <woody77@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] CeroWRT versions
Date: Sun, 13 Oct 2013 21:39:03 -0400	[thread overview]
Message-ID: <948F7121-0466-443E-9453-FB36EFE4DB4E@gmail.com> (raw)
In-Reply-To: <CAA93jw6-XkkVdS3aXwK7uTHSXqavO30Ooaah0cGdEPKKFc3DTQ@mail.gmail.com>

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

Folks,

Unless someone else already has this under control, I'm willing to pull together a set of release notes that indicate the major enhancements that have occurred between 3.7 and 3.10, as well as a (near) current list of the major packages that are included. 

I'll post these on the CeroWrt wiki shortly, and we can get them caught up to the current state of development, so that we have a good ReadMe and set of Release Notes available when the software gets to a stable state.

Rich

On Oct 12, 2013, at 10:06 PM, Dave Taht <dave.taht@gmail.com> wrote:

> 
> On Oct 13, 2013 12:37 AM, "Aaron Wood" <woody77@gmail.com> wrote:
> >
> > What are the compelling reasons to try versions newer than 3.7.5-2?  I'm using a WNDR3800.
> 
> Masochism?
> 
> More seriously, without cerowrt's cadre of dedicated testers we'd never get to a release stable enough for mom to use.  There is quite a long 
> List of improvements since 3.7.
> 
> Regrettably at the moment there are two nasty regressions so bad that I don't recommend anything more recent than 3.10.11-3.
> 
> > And I can't seem to find release notes for anything newer than that (but e-mail notifications to the devel mailing list).
> 
> Everything since that version has been a development build and usually an artifact of the continuous integration process.
> 
> If I don't announce it on the list here it was compile tested only.
> 
> If I test a little and announce it I try to put in short release notes here.
> 
> ...
> 
> It was my hope to have got a new stable release in august. Didn't make it, was busy on paid stuff in sept...
> 
> In lui of release notes I should put up a roadmap... And I'm setting aside more time for this in the coming weeks in the hope we can resolve the last sticky bugs before ietf. At which point the website would get updates etc.
> 
> > Thanks,
> > Aaron Wood
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
> >
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #2: Type: text/html, Size: 3036 bytes --]

           reply	other threads:[~2013-10-14  1:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAA93jw6-XkkVdS3aXwK7uTHSXqavO30Ooaah0cGdEPKKFc3DTQ@mail.gmail.com>]

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=948F7121-0466-443E-9453-FB36EFE4DB4E@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=woody77@gmail.com \
    /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