<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hey Arlo! Stop Breaking Features with Your Updates in Arlo</title>
    <link>https://community.arlo.com/t5/Arlo/Hey-Arlo-Stop-Breaking-Features-with-Your-Updates/m-p/1748091#M73731</link>
    <description>&lt;P&gt;It's become apparent that Arlo is struggling with their software branch/department regarding establishing some kind of control over why and when to upgrade software.&amp;nbsp; My suggestion is that when a software change is made that removes, or causes problems with, useful features that it should be considered a bad thing to do.&amp;nbsp; Just saying.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Dec 2019 15:37:23 GMT</pubDate>
    <dc:creator>MaHe01</dc:creator>
    <dc:date>2019-12-24T15:37:23Z</dc:date>
    <item>
      <title>Hey Arlo! Stop Breaking Features with Your Updates</title>
      <link>https://community.arlo.com/t5/Arlo/Hey-Arlo-Stop-Breaking-Features-with-Your-Updates/m-p/1748091#M73731</link>
      <description>&lt;P&gt;It's become apparent that Arlo is struggling with their software branch/department regarding establishing some kind of control over why and when to upgrade software.&amp;nbsp; My suggestion is that when a software change is made that removes, or causes problems with, useful features that it should be considered a bad thing to do.&amp;nbsp; Just saying.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Dec 2019 15:37:23 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo/Hey-Arlo-Stop-Breaking-Features-with-Your-Updates/m-p/1748091#M73731</guid>
      <dc:creator>MaHe01</dc:creator>
      <dc:date>2019-12-24T15:37:23Z</dc:date>
    </item>
  </channel>
</rss>

