From: Dave Taht <dave.taht@gmail.com>
To: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Codel] Fwd: [Ns-developers] ns-2.36 release candidate available for testing
Date: Sun, 21 Dec 2014 12:27:12 -0800 [thread overview]
Message-ID: <CAA93jw4XKbTUrYKAGS9OOq_eCbwhw_8PbAar3+srx+F7WQ=QkQ@mail.gmail.com> (raw)
In-Reply-To: <54972C0F.8090806@tomh.org>
I have not had time to test much of all the aqm and packet scheduling
stuff that has landed in ns2 mainline, personally. Hopefully all of
you out there using out of tree patches can try what has been
mainlined to see what, if anything broke. Please direct replies and
feedback at the ns-developers list, not here.
---------- Forwarded message ----------
From: Tom Henderson <tomh@tomh.org>
Date: Sun, Dec 21, 2014 at 12:22 PM
Subject: [Ns-developers] ns-2.36 release candidate available for testing
To: ns-developers list <ns-developers@isi.edu>, "ns-users@isi.edu"
<ns-users@isi.edu>
Hi all, I'm preparing to release a new ns-2 version, numbered ns-2.36.
There is a wiki page and an initial release candidate posted here:
http://nsnam.isi.edu/nsnam/index.php/Roadmap
The main differences between ns-2.35 and ns-2.36 are the following:
* small fixes to the allinone 'install' script to build on current systems
* a variety of changes to ns-2 source code and build scripts to
compile on newer gcc and also clang-based systems
* new AQM and cable system models, including CoDel, SFQCoDel,
CoDel-DT, PIE, and DocsisLink
* a Bonnmotion mobility example
I would like to release this by the second half of January. There are
a few open issues that might lead to some updates, including the RED
issue I just mailed about; the currently open issues are listed on the
wiki page.
If you would like to suggest changes, or find problems with these
release candidates, please let us know on the ns-developers mailing
list, or contact me off list.
Thanks,
Tom
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
parent reply other threads:[~2014-12-21 20:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54972C0F.8090806@tomh.org>]
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4XKbTUrYKAGS9OOq_eCbwhw_8PbAar3+srx+F7WQ=QkQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@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