From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] bql-27 smoketest released, with... BQL, SFQRED, etc
Date: Wed, 1 Feb 2012 14:45:37 +0000 [thread overview]
Message-ID: <CAA93jw6gkVYfp9uo6_bHCDoTL7x=FS8Rzu6rww9FpzF5+fEaNA@mail.gmail.com> (raw)
In-Reply-To: <37D587BA-8893-4CE5-B49B-331C86ECE55C@intermapper.com>
On Wed, Feb 1, 2012 at 1:18 PM, Richard Brown
<richard.e.brown@dartware.com> wrote:
> Dave,
>
>>> Mentally 'Paris' is the upcoming build.
>
> Then we should build on this. I'll propose this description:
>
> The "Paris" build has an excellent first-cut at eliminating the problems caused by bufferbloat. It may not be the final word on the subject, but it's a serious stake in the ground. Subsequent major releases (with further improvements) will have some other city name.
>
>>> I would like to get away from the 'rc' nomenclature. I'm open to a new
>>> naming and numbering scheme for sure.
>
> It has always been confusing to have the profusion of directories in http://huchra.bufferbloat.net/~cero1/ I know the reasons, but simplification would help. Maybe we should just have two:
> - Paris
> - OlderBuilds
Can't change the directory structure around without breaking opkg updates.
Probably better to start publishing a new toplevel dir entirely,
perhaps something like http://cerowrt.bufferbloat.net, with
"Ocean_City", "Paris", "Development" subdirs.
>
> The Paris directory contains current stuff. There can be Stable and Development subdirectories. Once we get something that's pretty good, we move it to the Stable directory that people can use with safety. Development gets whatever untested, unstable version that's currently in source control.
>
> The OlderBuilds just contains the set of directories that are currently at the top level. They're for historical interest only.
>
> Does this work?
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-02-01 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1328040001.13547.cerowrt-devel@lists.bufferbloat.net>
2012-02-01 3:42 ` Richard Brown
2012-02-01 4:24 ` Dave Taht
2012-02-01 5:34 ` Richard Brown
2012-02-01 5:46 ` Dave Taht
[not found] ` <CAA93jw4t=b3ZBhtrJLZiGbZiCBzG71HZovWTO4NV5Kreic96=g@mail.gmail.com>
2012-02-01 13:18 ` Richard Brown
2012-02-01 14:45 ` Dave Taht [this message]
2012-02-01 15:12 ` Richard Brown
2012-02-01 5:39 ` [Cerowrt-devel] Figure of Merit Richard Brown
2012-02-01 6:04 ` Dave Taht
2012-01-30 22:38 [Cerowrt-devel] bql-27 smoketest released, with... BQL, SFQRED, etc Dave Taht
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='CAA93jw6gkVYfp9uo6_bHCDoTL7x=FS8Rzu6rww9FpzF5+fEaNA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richard.e.brown@dartware.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