Roadmap: Difference between revisions

From Nsnam
Jump to navigation Jump to search
No edit summary
 
(66 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{TOC}}
{{TOC}}


This page summarizes the release roadmap for ns-3.  A summary of current development activities can be found [[Current Development|here]].
ns-3 is a community-driven project, and as such, we cannot typically make guarantees about the availability of new or improved code; our maintainers work largely on a best-effort basisHowever, we use this page to describe our goals (time-permitting) for each release, and where we broadly are trying to steer the project for the future.


__FORCETOC__
== ns-3.48 plans ==


== Release schedule ==
ns-3.48 is scheduled for May 2026.


ns-3 plans regular date-driven (not feature driven) releases. ns-3 stable releases are sequentially numbered starting with minor version 1 (ns-3.1, released June 30 2008).
The most up-to-date listing of items being worked on in this release cycle can be seen by browsing [https://gitlab.com/nsnam/ns-3-dev/-/merge_requests?scope=all&state=opened&milestone_title=ns-3.48 Merge requests] and [https://gitlab.com/nsnam/ns-3-dev/-/issues?scope=all&state=opened&milestone_title=ns-3.48 Issues] in the GitLab.com tracker that are tagged with the 'Milestone ns-3.48' tag.


=== ns-3.3 ===
Besides this, the following [https://www.nsnam.org/about/governance/maintainers/ ns-3 maintainers] announced plans to work on the following topics:


ns-3.3 is tentatively scheduled for November, and will pick up as many of the projects under [[Current Development]] as are ready. More details will be posted at the beginning of October.
* Tom Henderson is prioritizing:
** Supporting wifi (and eventual ns-3-dev) transition to strongly-typed quantities and units
** Merging GSoC 2025 code [https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/2571 Orbital NTN] and [https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/2482 6LoWPAN ND]
** Seeing if we can revive [https://github.com/direct-code-execution/ns-3-dce/pull/147 ns-3 DCE]
** Working on issue and MR backlog
* Biljana Bojovic from the highest to the lowest priority:
** Reviewing Sionna MR https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/2608
** Try to revive NGMN traffic generators MR: https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/2245
** Help with other ns-3 MR backlog
** Would like to work also on:
*** the precoding matrix conversion modelling options
*** check if feasible to port some 3GPP models calibration scripts to ns-3
*** ns-3 with GPUs
*** LLMs for 5G-LENA doxygen


== Release process ==  
== Long term ==


ns-3 releases are based on date-driven schedules: rather than target a set of features for a specific version number, we aim instead for a release date and ship whatever is ready by that date. If a cool new feature misses that date, it is not a big deal because the next release is never too far away. The current interval between releases is about 3 months.
== Historical information ==


The goal is to document what we would like to see in a number of releases, but, of course, since this is an Open Source project, contributors are free to work on anything they are interested in and try to merge it in earlier than stated. If we feel a specific feature targeted to a specific release just won't make it in time, we will move that feature to the next release.
see the [[Current_Development]] page for some older Roadmap items (many have been abandoned)
 
Some of the items in this roadmap do not have anyone signed up to get work done on them. So, there is something you are interested in, ask on ns-developers.
 
Detailed steps for doing the source code release are found in the [http://code.nsnam.org/ns-3-dev/file/1e8249c58fda/doc/release_steps.txt doc/release_steps.txt] file in the ns-3-dev repository. 
 
=== Deadlines ===
 
There are a few deadlines and steps for incorporating code into a scheduled ns-3 release:
 
* '''(15 days prior)''' deadline for posting any patches or private repos that are solicited for review/comment, for possible check in to the upcoming release.  These are for patches or repos that can be considered as extensions to the simulator.  Post a summary to the list, allow 7 days (minimum) for comments, and if all comments and issues can be resolved in that time window, it can go into the next release; otherwise it slides until when things are resolved.
* '''(7 days prior)''' deadline for being in a "ready-to-merge" state, which means that there is agreement that comments from the previous stage have been resolved and that the change can go in.  Perhaps a "last-call" announcement by the release manager on the list will help.
* '''(3 days prior)''' deadline for merging any extensions or new modules that change the API, or any miscellaneous changes by maintainers.  Exceptions: critical bug fixes, doxygen and documentation, and coding style alignment nits.
 
Finally, it is good practice to announce among the active committers when you are doing a major merge, to avoid bad merge collisions.

Latest revision as of 09:05, 19 March 2026

Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects

HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers

ns-3 is a community-driven project, and as such, we cannot typically make guarantees about the availability of new or improved code; our maintainers work largely on a best-effort basis. However, we use this page to describe our goals (time-permitting) for each release, and where we broadly are trying to steer the project for the future.

ns-3.48 plans

ns-3.48 is scheduled for May 2026.

The most up-to-date listing of items being worked on in this release cycle can be seen by browsing Merge requests and Issues in the GitLab.com tracker that are tagged with the 'Milestone ns-3.48' tag.

Besides this, the following ns-3 maintainers announced plans to work on the following topics:

Long term

Historical information

see the Current_Development page for some older Roadmap items (many have been abandoned)