<?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 Runtime 18 LTS and change of naming convention in MVP Articles</title>
    <link>https://community.databricks.com/t5/mvp-articles/runtime-18-lts-and-change-of-naming-convention/m-p/164892#M271</link>
    <description>&lt;P&gt;19 is already here, but 18 is now LTS. In a new naming convention, LTS doesn’t have a minor version. New features, behavior changes, and fixes are now added incrementally to the same major Runtime version till it becomes LTS. In fact, that approach simplifies the problem with editing code and always thinking which LTS it was, 18.3 or 18.2? Now just put 18.x in your DABs.&lt;/P&gt;
&lt;P&gt;more news &lt;A class="relative pointer-events-auto a
  
  
  
  
  underline
  
  cursor-pointer" href="https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f" rel="noopener nofollow ugc" target="_blank"&gt;https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f&lt;/A&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lts18.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/29750i3425E15E65DA777B/image-size/large?v=v2&amp;amp;px=999" role="button" title="lts18.png" alt="lts18.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Aug 2026 22:12:15 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2026-08-04T22:12:15Z</dc:date>
    <item>
      <title>Runtime 18 LTS and change of naming convention</title>
      <link>https://community.databricks.com/t5/mvp-articles/runtime-18-lts-and-change-of-naming-convention/m-p/164892#M271</link>
      <description>&lt;P&gt;19 is already here, but 18 is now LTS. In a new naming convention, LTS doesn’t have a minor version. New features, behavior changes, and fixes are now added incrementally to the same major Runtime version till it becomes LTS. In fact, that approach simplifies the problem with editing code and always thinking which LTS it was, 18.3 or 18.2? Now just put 18.x in your DABs.&lt;/P&gt;
&lt;P&gt;more news &lt;A class="relative pointer-events-auto a
  
  
  
  
  underline
  
  cursor-pointer" href="https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f" rel="noopener nofollow ugc" target="_blank"&gt;https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f&lt;/A&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lts18.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/29750i3425E15E65DA777B/image-size/large?v=v2&amp;amp;px=999" role="button" title="lts18.png" alt="lts18.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2026 22:12:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/mvp-articles/runtime-18-lts-and-change-of-naming-convention/m-p/164892#M271</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2026-08-04T22:12:15Z</dc:date>
    </item>
  </channel>
</rss>

