Twelve years ago, we introduced a new way of delivering PureBasic by implementing an LTS (Long-Term Support) version, which received bug fixes for two years (see this blog post for more details). At that time, the release process was relatively simple:

• 2 Linux packages
• 2 Windows packages
• 2 macOS packages

Additionally, major releases that introduced breaking changes were more frequent.

Fast forward to today, managing PureBasic across platforms has become significantly more complex:

• 4 Linux packages (each with both ASM and C backends)
• 2 Raspberry Pi packages
• 2 macOS packages (one with ASM and C backend)
• 3 Windows packages (each with both ASM and C backends)

This increase in complexity has made the build process far more time-consuming. As a small team, maintaining both the LTS and regular versions—while ensuring bug fixes are properly merged and retested across branches—has become unsustainable.

Meanwhile, the PureBasic API has matured, resulting in fewer breaking changes with each major version. As a result, the need for an LTS version has diminished.

Going forward, our plan is to follow each major release with one or more minor updates to fix any new bugs. This approach should provide a stable production environment while ensuring smooth, hassle-free migration from one major version to the next.