What is the release versioning strategy ? Is there a long-term upgrade path?

Hi there, We are making the jump to self-hosted Twenty this week. Before we do, I have two concerns regarding the update process and long-term maintenance. 1) Release versioning and cadence The versioning logic for Twenty CRM is unclear to me. Most open-source projects follow standard Semantic Versioning — 2.X.Y, where X introduces new features and Y covers minor improvements and bug fixes. With Twenty CRM, I'm seeing versions like 2.7.0, 2.8.0, 2.8.1, 2.8.2, and 2.8.3 all appearing within the same 7 days. Could you help clarify what drives this cadence and how stable a given release is considered to be at the time of publication? 2) Upgrade path and lifecycle planning A CRM sits at the core of a company's operations, it cannot be out of order for 8 hours, so being able to plan ahead around update policies and version lifecycle is critical. Other mature open-source projects — such as Ubuntu or SuiteCRM — publish roadmaps and clearly distinguish between short-l…