<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zigbee stability &amp;amp; scalability issues: nRF5 SDK vs nRF Connect SDK migration</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128160/zigbee-stability-scalability-issues-nrf5-sdk-vs-nrf-connect-sdk-migration</link><description>Good morning Nordic team, we are currently evaluating a migration of our Zigbee firmware from the legacy nRF5 SDK for Thread &amp;amp; Zigbee v4.2.0 to the nRF Connect SDK (Zephyr-based) on the nRF52840, and we would like your technical feedback before proceeding</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 10:43:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128160/zigbee-stability-scalability-issues-nrf5-sdk-vs-nrf-connect-sdk-migration" /></channel></rss>