New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network stack refactoring: TODO list #2278

Closed
miri64 opened this Issue Jan 12, 2015 · 6 comments

Comments

Projects
None yet
3 participants
@miri64
Member

miri64 commented Jan 12, 2015

Next steps (as result from the network stack task force meeting):

All new modules are to be prepended with the prefix ng_.

Open topics

  • adjust CC2420 radio
  • adjust CC1100 radio
  • ICMPv6 error messages [under review -> #3184]
  • Redirect behavior of NDP
  • reimplement sockets [merged -> #3646]

@miri64 miri64 added this to the Release NEXT MAJOR milestone Jan 12, 2015

@miri64 miri64 changed the title from netapi: Port all layers to netapi or create new modules using netapi to Network stack refactoring: TODO list Jan 12, 2015

@OlegHahm OlegHahm added the GNRC label Feb 6, 2015

@OlegHahm OlegHahm modified the milestones: Network Stack Task Force, Release NEXT MAJOR Feb 6, 2015

@OlegHahm OlegHahm added GNRC and removed GNRC labels Feb 6, 2015

@miri64

This comment has been minimized.

Show comment
Hide comment
@miri64

miri64 Feb 8, 2015

Member

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Member

miri64 commented Feb 8, 2015

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

@miri64

This comment has been minimized.

Show comment
Hide comment
@miri64

miri64 Feb 19, 2015

Member

The last critical component was merged. From now on it's Happy Hacking!

Member

miri64 commented Feb 19, 2015

The last critical component was merged. From now on it's Happy Hacking!

@OlegHahm

This comment has been minimized.

Show comment
Hide comment
@OlegHahm

OlegHahm Feb 19, 2015

Member

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Ah, haven't seen this before. Will do.

Member

OlegHahm commented Feb 19, 2015

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Ah, haven't seen this before. Will do.

@miri64

This comment has been minimized.

Show comment
Hide comment
@miri64

miri64 Mar 7, 2015

Member

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Just a little update on my rational for assigning the milestone: PR's or features that are explicitly mentioned here and any fix- or follow-up to those.

Member

miri64 commented Mar 7, 2015

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Just a little update on my rational for assigning the milestone: PR's or features that are explicitly mentioned here and any fix- or follow-up to those.

@miri64

This comment has been minimized.

Show comment
Hide comment
@miri64

miri64 Sep 23, 2015

Member

Updated list.

Member

miri64 commented Sep 23, 2015

Updated list.

@miri64

This comment has been minimized.

Show comment
Hide comment
@miri64

miri64 Oct 17, 2016

Member

Though there are still some things under construction, since PRs exist I would deem this issue as complete, so close.

Member

miri64 commented Oct 17, 2016

Though there are still some things under construction, since PRs exist I would deem this issue as complete, so close.

@miri64 miri64 closed this Oct 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment