Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Rebasing, rescheduling and rethinking cerowrt
Date: Sun, 4 Dec 2011 09:37:50 +0100	[thread overview]
Message-ID: <CAA93jw5jKR503xzeLO_XMfveQY-5k2Kz6aOR4Cwf7T4pMjbGhw@mail.gmail.com> (raw)

I am in the process of rebasing cerowrt on openwrt head,
reworking and cleaning up the patches that were good
and submitting those to the maintainers, and doing
a rethink as to how to proceed forward for rc8 given
all the (positive!) bufferbloat related churn in the
linux 3.2 and 3.3 development processes.

Too much changed out from under Cerowrt-rc7 to
deliver a stable release.

It IS serving it's original
purpose in being a R&D platform for inquiring
into bufferbloat and the difficulties home gateways
face in the coming decade admirably, but, a thorough
review  of the roadmap for rc8 shows
several man years of development is required
to deliver everything on that list, and that list
is incomplete at best.

http://www.bufferbloat.net/projects/cerowrt/roadmap

This is a major problem. Something has to give.
Yet there's some really good stuff in there. In
particular the new AQMs are looking promising,
as is BQL.

The cerowrt repository on github has been renamed to
Cerowrt-rc7. There will not be a 'final' rc7 release.

There will not be a public cerowrt-rc8 repo
for a while, either, while we get the above sorted out.

If you have any out of tree updates to cerowrt-rc7 and
would like them considered for rc8, please submit
them to the cerowrt-devel list.

This will be the last message to the bloat-devel list
regarding the cerowrt development process. Future
cross postings will stay focused on bloat related
R&D. I will also be adding some infrastructure for
postings to cerowrt-commits and more automated
builds in the hope of reducing the administrative
burden somewhat.

Any suggestions on how to better maintain and
interoperate with source trees kept in svn and git,
incorporating hundreds of packages, and still find
a decent way to hit one button and build an OS
are AND still move constructively forward
with innovative R&D are *welcomed*.

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net

                 reply	other threads:[~2011-12-04  8:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw5jKR503xzeLO_XMfveQY-5k2Kz6aOR4Cwf7T4pMjbGhw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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