Hi, Kaspar - is the Trifecta port already providing the new network stack? Is there any reason we shouldn't move ahead to the latest commit?
I got a notice that your invoices have been received and are in process. I think you've completed everything on the SoW and we don't know of any outstanding bugs or questions. I've tested the IPv6 stack in your example app, and we've been able to build and run our ICN code on the Trifecta modules. Have you included all of your work on the two invoices; if so, I'll close out the PO as completed. At some point, we'll need to arrange to have the CU you've been using shipped back to us. Perhaps we should leave it with you for a few weeks in case run into any issues? - Ralph > On Aug 6, 2015, at 9:44 AM, Kaspar Schleiser <kas...@schleiser.de> wrote: > > Hello RIOTers, > > as announced, we've merged the PR that removes the old network stack. > > The last commit before removal is > > 68d05197319c2645bd88f0242426fad4e96cf4e2 > > Issue #3417 [1] shows dropped functionality. Also, we've started a > wiki-page [2] collecting features we're removing due to lack of > resources, but the page is a little short on content at the moment. > > Happy hacking! > Kaspar & Hauke > > [1] https://github.com/RIOT-OS/RIOT/issues/3417 > [2] https://github.com/RIOT-OS/RIOT/wiki/Removed-Features > > >> On 07/28/15 21:22, Oleg Hahm wrote: >> Hello RIOTers, >> >> on the last bi-weekly developer meeting, we've decided to >> 1.) start a beta-test period for the new gnrc network stack and >> 2.) remove the old network stack from our master tree. >> >> ad 1.) >> The new network stack, also known as generic or gnrc stack, is intended to >> become the default network (IPv6) stack for RIOT within the next couple of >> weeks. >> Thanks to the tremendous work of the NSTF (network stack task force) the >> stack >> has finally reached a state where you can run a full IP stack (from UDP down >> to PHY) as well on native (Ethernet and plain IPv6) as on real (802.15.4 >> capable) hardware (6LoWPAN). >> >> In order to converge to a stable state as fast as we can, help for testing, >> finding and fixing bugs is highly appreciated. >> >> We would like to invite the whole RIOT community to check out the current >> master and play around with gnrc features as a kind of beta testing. >> >> ad 2.) >> Since the gnrc stack is meant to replace the current IPv6 stack, we've >> decided >> to remove this stack already now. For a summary of pro/con arguments please >> check the meeting minutes. [1] >> >> One week from now (Wed 05.08.), we will tag the last commit that contains the >> old network stack, and then merge a removal PR (probably #3334 [2]). >> >> Issue #3417 [3] will be used to track removed functionality. >> >> If you have important arguments against removing the old stack, speak up! >> >> Kaspar and Oleg >> >> [1] http://riot.pad.spline.de/15 >> [2] https://github.com/RIOT-OS/RIOT/pull/3334 >> [3] https://github.com/RIOT-OS/RIOT/issues/3417 >> >> >> >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel >> > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
