<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ci on Murat Useinov</title>
    <link>https://useinov.com/tags/ci/</link>
    <description>Recent content in Ci on Murat Useinov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 30 Nov 2018 15:15:00 +0300</lastBuildDate>
    <atom:link href="https://useinov.com/tags/ci/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deprecations are a to-do list, not noise</title>
      <link>https://useinov.com/posts/2018/deprecation-budget/</link>
      <pubDate>Fri, 30 Nov 2018 15:15:00 +0300</pubDate>
      <guid>https://useinov.com/posts/2018/deprecation-budget/</guid>
      <description>&lt;p&gt;&lt;code&gt;SYMFONY_DEPRECATIONS_HELPER=&#39;max[total]=20&#39; ./bin/phpunit&lt;/code&gt;. Twenty is the number of deprecation warnings we had on the day we started counting. The rule is that it only goes down.&lt;/p&gt;
&lt;p&gt;Symfony 4.2 came out yesterday, on the six month schedule. With this cadence deprecation warnings stop being an event and become weather. Every minor release brings a new batch, teams train themselves not to see them, and that is a mistake, because a deprecation is the next major upgrade delivered early, in small pieces, with instructions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
