starting the ns-3.27 release process

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

starting the ns-3.27 release process

Tom Henderson-2
Hi all,
I would like to initiate planning and reviewing for ns-3.27.  I would
like to make this release before the end of the year.  This means that
we have about a month and a half to work on new features or more
intrusive changes.  There are plenty of items in the queue, so if anyone
would like to advocate for finishing off and merging a particular issue,
please work with me to push things along.

The wiki page for ns-3.27 activity and status is:
https://www.nsnam.org/wiki/Ns-3.27

I plan to have weekly updates to close out issues and to request
feedback on new issues (those that can't be handled simply by a
maintainer).  I'll get this started for this week with two requests for
review and feedback.

1) we had a proposed web browsing traffic generator that seems close to
being ready.  Here is the original email:
http://mailman.isi.edu/pipermail/ns-developers/2015-April/012668.html

Are there any further comments on this or should we move towards
finishing off the loose ends and getting it merged?

2) I would like to change the default timestamp resolution on logging
output to nanosecond precision.  There are a few possible ways to
implement.  Anyone care to chime in on requirements or preferences?  See:

https://www.nsnam.org/bugzilla/show_bug.cgi?id=2490

Of course, there are many more issues being raised in the tracker (if
you want to be notified about all of these, please subscribe to the
ns-bugs mailing list), but this is an initial attempt to raise some
visibility of selected issues at the ns-developers level; we'll see how
it goes.


- Tom

p.s. ns-bugs mailing list: http://mailman.isi.edu/mailman/listinfo/ns-bugs

Reply | Threaded
Open this post in threaded view
|

Re: starting the ns-3.27 release process

Natale Patriciello
On 05/10/16 at 09:41pm, Tom Henderson wrote:
> Hi all,
> I would like to initiate planning and reviewing for ns-3.27.  I would like
> to make this release before the end of the year.  This means that we have
> about a month and a half to work on new features or more intrusive changes.
> There are plenty of items in the queue, so if anyone would like to advocate
> for finishing off and merging a particular issue, please work with me to
> push things along.
>

Hi Tom,

for what regards TCP I'd like to merge as soon as possible the SACK
implementation. By default, the SACK option will be turned to off; and
then let people play off / on. When I have your approval, I will merge
it.

> 1) we had a proposed web browsing traffic generator that seems close to
> being ready.  Here is the original email:
> http://mailman.isi.edu/pipermail/ns-developers/2015-April/012668.html
>
> Are there any further comments on this or should we move towards finishing
> off the loose ends and getting it merged?

I'd like to take a look on this tomorrow.

PS: Thank you and the team for the hard work for the release .26. Should
we prepare something for an eventual publication in a journal article
about the release ns3.26 (for instance, [1,2]) ?

[1] http://rescience.github.io/
[2] http://joss.theoj.org/

Nat
Reply | Threaded
Open this post in threaded view
|

Re: starting the ns-3.27 release process

Tom Henderson-2
On 10/06/2016 11:33 AM, Natale Patriciello wrote:

> On 05/10/16 at 09:41pm, Tom Henderson wrote:
>> Hi all,
>> I would like to initiate planning and reviewing for ns-3.27.  I would like
>> to make this release before the end of the year.  This means that we have
>> about a month and a half to work on new features or more intrusive changes.
>> There are plenty of items in the queue, so if anyone would like to advocate
>> for finishing off and merging a particular issue, please work with me to
>> push things along.
>>
>
> Hi Tom,
>
> for what regards TCP I'd like to merge as soon as possible the SACK
> implementation. By default, the SACK option will be turned to off; and
> then let people play off / on. When I have your approval, I will merge
> it.

Natale, is this the most current code?

https://github.com/kronat/ns-3-dev-git/tree/tcp-sack

If so, then yes, I would like to encourage final review of it-- is a
week sufficient for a last call?

>
>> 1) we had a proposed web browsing traffic generator that seems close to
>> being ready.  Here is the original email:
>> http://mailman.isi.edu/pipermail/ns-developers/2015-April/012668.html
>>
>> Are there any further comments on this or should we move towards finishing
>> off the loose ends and getting it merged?
>
> I'd like to take a look on this tomorrow.
>
> PS: Thank you and the team for the hard work for the release .26. Should
> we prepare something for an eventual publication in a journal article
> about the release ns3.26 (for instance, [1,2]) ?
>
> [1] http://rescience.github.io/
> [2] http://joss.theoj.org/

I'm new to these journals, but it might be something worth doing.  Are
you thinking that each release version has a new brief publication with
a DOI, including the authors who contributed to the release?

- Tom
Reply | Threaded
Open this post in threaded view
|

Re: starting the ns-3.27 release process

Natale Patriciello
On 06/10/16 at 05:07pm, Tom Henderson wrote:
> Natale, is this the most current code?
>
> https://github.com/kronat/ns-3-dev-git/tree/tcp-sack
>
> If so, then yes, I would like to encourage final review of it-- is a week
> sufficient for a last call?

Yes, it is; btw, I will add some flags to explicitly disable SACK on
the current tests that uses PCAP tracing.

> > PS: Thank you and the team for the hard work for the release .26. Should
> > we prepare something for an eventual publication in a journal article
> > about the release ns3.26 (for instance, [1,2]) ?
> >
> > [1] http://rescience.github.io/
> > [2] http://joss.theoj.org/
>
> I'm new to these journals, but it might be something worth doing.  Are you
> thinking that each release version has a new brief publication with a DOI,
> including the authors who contributed to the release?
>

Exactly. Is it worth? In my humble opinion, it could be interesting.

Natale
Reply | Threaded
Open this post in threaded view
|

Re: starting the ns-3.27 release process

Barnes, Peter D.
In reply to this post by Tom Henderson-2

On Oct 6, 2016, at 5:07 PM, Tom Henderson <[hidden email]<mailto:[hidden email]>> wrote:

PS: Thank you and the team for the hard work for the release .26. Should
we prepare something for an eventual publication in a journal article
about the release ns3.26 (for instance, [1,2]) ?

[1] http://rescience.github.io/
[2] http://joss.theoj.org/

I'm new to these journals, but it might be something worth doing.  Are you thinking that each release version has a new brief publication with a DOI, including the authors who contributed to the release?

- Tom

After a quick look [2] appears to be better suited for our releases, and gets my +.

Peter
_____________________________________________________________
Dr. Peter D. Barnes, Jr. NACS Division
Lawrence Livermore National Laboratory Physical and Life Sciences
7000 East Avenue, L-50 email:  [hidden email]<mailto:[hidden email]>
P. O. Box 808 Voice:  (925) 422-3384
Livermore, California 94550 Fax:    (925) 423-3371





Reply | Threaded
Open this post in threaded view
|

ns-3.27 update

Tom Henderson-2
In reply to this post by Tom Henderson-2
On 10/05/2016 09:41 PM, Tom Henderson wrote:

> Hi all,
> I would like to initiate planning and reviewing for ns-3.27.  I would
> like to make this release before the end of the year.  This means that
> we have about a month and a half to work on new features or more
> intrusive changes.  There are plenty of items in the queue, so if
> anyone would like to advocate for finishing off and merging a
> particular issue, please work with me to push things along.
>
> The wiki page for ns-3.27 activity and status is:
> https://www.nsnam.org/wiki/Ns-3.27

Hi again, the wiki page has been updated:
https://www.nsnam.org/wiki/Ns-3.27 <https://www.nsnam.org/wiki/Ns-3.27>

The 3GPP HTTP model code review issue and SACK repositories were updated
based on review comments.  I'd like to move towards including these
features as soon as the comments are resolved. Review feedback still
wanted for log timestamp format changes, and I posted in another message
about the request for review of summer projects; these are listed in the
current review items section of the ns-3.27 wiki page.

Recent checkins to ns-3-dev have included bug fixes for LTE,
propagation, and spectrum modules, and Sebastien continues to work on
the wifi module.

Discussions are also occurring, and new patches uploaded, on various
issues in the tracker; if you would like email notifications of these,
subscribe to ns-bugs: http://mailman.isi.edu/mailman/listinfo/ns-bugs

- Tom


Reply | Threaded
Open this post in threaded view
|

Re: ns-3.27 update

Tom Henderson-2
Hi all,
I am considering January 18 as a target date for ns-3.27.  I've updated
the wiki page with some status updates, although there are probably some
stale items still listed there.  Can maintainers please review and
suggest what needs to be adjusted?

https://www.nsnam.org/wiki/Ns-3.27

 From my perspective, replacement of gccxml with CastXML (Python
bindings) and contributed modules support are important for ns-3.27; on
the latter feature, a few of us are making progress to enable this.  TCP
SACK seems about ready to commit, and Sebastien is working to include
the WINLAB patch for Wifi frame capture models.

Please let us know if there are other open issues to prioritize.  If
anyone wants to take a specific open issue and run with it, please
contact me.  I've had some off list inquiries about how to help with
maintenance of certain modules; a good way to get started is to start
posting patches to try to close out open bugs.

- Tom