ns-3.27 release work

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

ns-3.27 release work

Tom Henderson-2
This is a brief update on the upcoming release.  We're currently
wrapping up a few new features that I'd like to see in this release,
including LTE Carrier Aggregation (in process of being merged this
week), TCP SACK, Wi-Fi frame capture, and bake extensions for
contributed modules.  There is also a lot of current work on wifi and
traffic-control modules as well, including initial 802.11ax components
and traffic control support for additional device types.  So I'd like to
leave the door open to get these merged over the next week or two, then
wrap up this release.  In the meantime, I will start to more
aggressively migrate patches in LAST CALL state into the codebase.

On the bake extensions, I will start a separate thread to discuss this.

- Tom
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ns-3.27 release work

Tom Henderson-2
On 01/20/2017 07:03 AM, Tom Henderson wrote:

> This is a brief update on the upcoming release.  We're currently
> wrapping up a few new features that I'd like to see in this release,
> including LTE Carrier Aggregation (in process of being merged this
> week), TCP SACK, Wi-Fi frame capture, and bake extensions for
> contributed modules.  There is also a lot of current work on wifi and
> traffic-control modules as well, including initial 802.11ax components
> and traffic control support for additional device types.  So I'd like
> to leave the door open to get these merged over the next week or two,
> then wrap up this release.  In the meantime, I will start to more
> aggressively migrate patches in LAST CALL state into the codebase.

We have had a lot of activity the past two weeks, including the merge of
LTE Carrier Aggregation and SACK, initial 802.11ax support, and many
wifi module issues fixed; thanks to Biljana, Sebastien, Matias, Nat, and
others for this recent progress.  We are also getting a large infusion
of Doxygen improvements from Robert Ammon (on tracker issue 938) that
Tommaso is migrating to ns-3-dev.

I would like also to try (although outstanding comments remain) to
include Wi-Fi frame capture model, the bake extensions for contributed
module (no new feedback received), and Stefano's queue rework, in this
upcoming release.  I know we have also many other code reviews recently
posted (TCP LEDBAT, traffic control extensions, and others) and I think
that we can merge some of these if they are ready now or soon, but I
would like to wrap up new features and move towards a release once the
above main features (contributed modules, queue rework, frame capture)
are resolved.

Please review the various queue proposals and Stefano's posts on the
subject: https://www.nsnam.org/bugzilla/show_bug.cgi?id=2633

I moved the bake/wscript extensions for contributed modules to LAST
CALL: https://www.nsnam.org/bugzilla/show_bug.cgi?id=2631 and
https://www.nsnam.org/bugzilla/show_bug.cgi?id=2630

- Tom
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ns-3.27 release work

Tom Henderson-2
Hi all, continuing this thread below.

On 02/03/2017 07:46 AM, Tom Henderson wrote:

> On 01/20/2017 07:03 AM, Tom Henderson wrote:
>> This is a brief update on the upcoming release.  We're currently
>> wrapping up a few new features that I'd like to see in this release,
>> including LTE Carrier Aggregation (in process of being merged this
>> week), TCP SACK, Wi-Fi frame capture, and bake extensions for
>> contributed modules.  There is also a lot of current work on wifi and
>> traffic-control modules as well, including initial 802.11ax
>> components and traffic control support for additional device types.  
>> So I'd like to leave the door open to get these merged over the next
>> week or two, then wrap up this release.  In the meantime, I will
>> start to more aggressively migrate patches in LAST CALL state into
>> the codebase.
>
> We have had a lot of activity the past two weeks, including the merge
> of LTE Carrier Aggregation and SACK, initial 802.11ax support, and
> many wifi module issues fixed; thanks to Biljana, Sebastien, Matias,
> Nat, and others for this recent progress.  We are also getting a large
> infusion of Doxygen improvements from Robert Ammon (on tracker issue
> 938) that Tommaso is migrating to ns-3-dev.
>
> I would like also to try (although outstanding comments remain) to
> include Wi-Fi frame capture model, the bake extensions for contributed
> module (no new feedback received), and Stefano's queue rework, in this
> upcoming release.  I know we have also many other code reviews
> recently posted (TCP LEDBAT, traffic control extensions, and others)
> and I think that we can merge some of these if they are ready now or
> soon, but I would like to wrap up new features and move towards a
> release once the above main features (contributed modules, queue
> rework, frame capture) are resolved.
>
> Please review the various queue proposals and Stefano's posts on the
> subject: https://www.nsnam.org/bugzilla/show_bug.cgi?id=2633
>
> I moved the bake/wscript extensions for contributed modules to LAST
> CALL: https://www.nsnam.org/bugzilla/show_bug.cgi?id=2631 and
> https://www.nsnam.org/bugzilla/show_bug.cgi?id=2630

Stefano recently revised and asked for review of his new queue
proposal.  Additional traffic control work hinges on these changes so I
would like to put them in LAST CALL for any further comments (I had a
look at them again this morning; please comment this week if you care or
else they will likely be merged as is).

Bin and Sebastien have been trying to converge on the details of the
frame capture model (issue 2368 in the tracker); I'm hopeful we can
still get that done over the next week.

We are also trying to get the static analysis and Doxygen patches all
into this release, and maybe some additional features in the tracker if
maintainers can get through them.

When will ns-3.27 be published?  I think we are looking at mid- to
late-March now, if we try to complete the above items by end of next
week.  Let's aim for closing out feature work by end of next week.

- Tom
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ns-3.27 release work

Tom Henderson-2
A brief update on the below

> Stefano recently revised and asked for review of his new queue
> proposal.  Additional traffic control work hinges on these changes so
> I would like to put them in LAST CALL for any further comments (I had
> a look at them again this morning; please comment this week if you
> care or else they will likely be merged as is).

I'd like to ask Stefano to proceed with this merge.
>
> Bin and Sebastien have been trying to converge on the details of the
> frame capture model (issue 2368 in the tracker); I'm hopeful we can
> still get that done over the next week.
Sebastien has been working on this over the past few days; we are still
trying to slip this in.  He is also interested in finishing off issues
2399, 2460, and 2470.
>
> We are also trying to get the static analysis and Doxygen patches all
> into this release, and maybe some additional features in the tracker
> if maintainers can get through them.

I still would like to get all of these patches merged before release.  
Biljana has been working on LTE related ones; if any other maintainers
plan to work on merging in their module(s), please let me know;
otherwise I'll do it or get some help.

>
> When will ns-3.27 be published?  I think we are looking at mid- to
> late-March now, if we try to complete the above items by end of next
> week.  Let's aim for closing out feature work by end of next week.
>
> - Tom


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ns-3.27 release work

Stefano Avallone
On mercoledì 8 marzo 2017 16:05:15 CET Tom Henderson wrote:
> A brief update on the below
>
> > Stefano recently revised and asked for review of his new queue
> > proposal.  Additional traffic control work hinges on these changes so
> > I would like to put them in LAST CALL for any further comments (I had
> > a look at them again this morning; please comment this week if you
> > care or else they will likely be merged as is).
>
> I'd like to ask Stefano to proceed with this merge.

Done, thank you for reviewing and giving the green flag.

I tested the current ns-3-dev on the following platforms:

- Linux 64-bit, clang++ 3.9.1
- Linux 64-bit, g++ 6.3.1
- Linux 64-bit, g++ 4.9.4
- Mac OSX, Apple LLVM 8.0.0

We shall recall to raise the requirement on g++ to 4.9 because the standard
library shipped with 4.8 does not provide the C++11 variant of
std::list::insert and std::list::erase that accepts a const iterator.

Bests,
Stefano


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ns-3.27 release work

Tom Henderson-2
On 03/08/2017 09:39 AM, Stefano Avallone wrote:

> On mercoledì 8 marzo 2017 16:05:15 CET Tom Henderson wrote:
>> A brief update on the below
>>
>>> Stefano recently revised and asked for review of his new queue
>>> proposal.  Additional traffic control work hinges on these changes so
>>> I would like to put them in LAST CALL for any further comments (I had
>>> a look at them again this morning; please comment this week if you
>>> care or else they will likely be merged as is).
>> I'd like to ask Stefano to proceed with this merge.
> Done, thank you for reviewing and giving the green flag.
>
> I tested the current ns-3-dev on the following platforms:
>
> - Linux 64-bit, clang++ 3.9.1
> - Linux 64-bit, g++ 6.3.1
> - Linux 64-bit, g++ 4.9.4
> - Mac OSX, Apple LLVM 8.0.0
>
> We shall recall to raise the requirement on g++ to 4.9 because the standard
> library shipped with 4.8 does not provide the C++11 variant of
> std::list::insert and std::list::erase that accepts a const iterator.

Stefano, I've updated the minimal compiler versions listed on the wiki
and in the coding style document, and added some pointers on the wiki
for upgrading gcc on older CentOS and Ubuntu releases.  I also noted the
upgrade requirement in the RELEASE_NOTES.

Thanks,
Tom

Loading...