Predictable stable release cadence for self-hosted deployments

I appreciate the pace of development and the work the Twenty CRM team is doing. However, the current release frequency is becoming difficult to manage for self-hosted deployments. When I began self-hosting Twenty CRM in September 2025, updates appeared to follow a roughly 4 to 6 week pattern. That made it practical to schedule maintenance every 6 to 8 weeks without falling significantly behind. Over the past year, releases appear to have accelerated from every few weeks, to every couple of weeks, to weekly, and now sometimes multiple releases in a single week. For a self-hoster, missing updates for only 2 or 3 weeks can mean being many versions behind. Frequent releases are understandable, especially with faster development workflows, but self-hosted operators need a more predictable and stable upgrade path. The current pace makes it difficult to properly review release notes, plan downtime, validate backups, test upgrades, and schedule maintenance. It is also concerning when rele…