NDN project issue tracking system: Issueshttps://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232018-02-20T11:25:40ZNDN project issue tracking system
Redmine ndnSIM - Task #4514 (Closed): Update underlying NFD and ndn-cxx version to 0.6.1https://redmine.named-data.net/issues/45142018-02-20T11:25:40ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #4311 (Closed): Upgrade NS-3 to the latest versionhttps://redmine.named-data.net/issues/43112017-09-28T15:28:27ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #4306 (Closed): Upgrade to NFD and ndn-cxx 0.6.0https://redmine.named-data.net/issues/43062017-09-27T20:32:02ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3881 (Closed): HopCount as a tag of an Interest and Data packethttps://redmine.named-data.net/issues/38812016-12-06T15:18:47ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3877 (Closed): Write release notes for ndnSIM 2.3https://redmine.named-data.net/issues/38772016-12-05T15:43:15ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3876 (Closed): Update documentation for the release of ndnSIM 2.3https://redmine.named-data.net/issues/38762016-12-05T15:34:23ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3875 (Closed): Update NFD + ndn-cxx to version 0.5https://redmine.named-data.net/issues/38752016-12-05T11:02:12ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3873 (Closed): Make unit test compatible with ndnSIM-specific transporthttps://redmine.named-data.net/issues/38732016-12-01T15:24:52ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3872 (Closed): Add tracing functionality of network-layer NACKshttps://redmine.named-data.net/issues/38722016-12-01T13:48:22ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3871 (Closed): Create an ndnSIM-specific Transport abstraction for NFD Face systemhttps://redmine.named-data.net/issues/38712016-12-01T13:44:41ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3837 (Closed): Create helper to select the replacement policy for NFD's CShttps://redmine.named-data.net/issues/38372016-11-02T15:20:50ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3835 (Closed): Update documentation for ndnSIM 2.2 releasehttps://redmine.named-data.net/issues/38352016-10-31T13:54:08ZSpyros Mastorakisspiros.mastorakis@gmail.comndnSIM - Task #3832 (Closed): Prepare release of version 2.2https://redmine.named-data.net/issues/38322016-10-28T19:19:12ZSpyros Mastorakisspiros.mastorakis@gmail.com
<p>This issue includes tasks:</p>
<ol>
<li>Write release notes, mentioning new features and updates</li>
<li>Update documentation </li>
<li>Update and release of new version of TR. Include the fact that we do not support yet NDNLPv2 in order to preserve NS-3 packet tags</li>
</ol>
ndnSIM - Task #3560 (Closed): Update ndn-cxx and NFD submodules to 0.4.1 or abovehttps://redmine.named-data.net/issues/35602016-03-22T16:35:57ZSpyros Mastorakisspiros.mastorakis@gmail.comChronoSync - Task #3224 (New): Renaming common.hpp to common-chronosync.hpphttps://redmine.named-data.net/issues/32242015-09-23T16:28:20ZSpyros Mastorakisspiros.mastorakis@gmail.com
<p>I have been trying to port the latest version of ChronoSync to ndnSIM 2.1 and I am facing a name conflict among common.hpp of ChronoSync and common.hpp of NFD and ndn-cxx. Could I submit a patch renaming the common.hpp file of ChronoSync to common-chronosync.hpp in order to avoid this conflict? I would like to attach the master branch of the official ChronoSync repo as a submodule to my template scenario, so that I can retrieve the latest changes without the need to rebase and maintain a personal ChronoSync repo that would be time-consuming.</p>