<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Meta on Deltablot</title><link>https://www.deltablot.com/tags/meta/</link><description>Recent content in Meta on Deltablot</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Apr 2026 02:12:55 +0100</lastBuildDate><atom:link href="https://www.deltablot.com/tags/meta/index.xml" rel="self" type="application/rss+xml"/><item><title>eLabFTW release schedule</title><link>https://www.deltablot.com/posts/release-schedule/</link><pubDate>Sat, 18 Apr 2026 02:12:55 +0100</pubDate><guid>https://www.deltablot.com/posts/release-schedule/</guid><description>&lt;h1 id="elabftw-release-schedule"&gt;eLabFTW release schedule&lt;/h1&gt;
&lt;p&gt;eLabFTW follows a frequent release model: new minor versions are published regularly, and patch releases are issued when needed. We do not provide Long Term Support (LTS) versions.&lt;/p&gt;
&lt;p&gt;This post explains why.&lt;/p&gt;
&lt;h2 id="release-schedules-are-a-tradeoff"&gt;Release schedules are a tradeoff&lt;/h2&gt;
&lt;p&gt;Software projects adopt many different release strategies. Some publish major versions on a fixed schedule. Some release continuously. Others have long gaps between releases.&lt;/p&gt;
&lt;p&gt;No single approach is objectively best. Each model comes with tradeoffs between stability, maintenance effort, development speed, and security response. The right choice depends on the nature of the software and the resources available to maintain it.&lt;/p&gt;</description></item></channel></rss>