We provide support for older versions of our software for one year following the release of a new major version in order to balance continuity for existing users with the practical realities of long-term software maintenance. Ongoing support is inherently expensive: it requires dedicated engineering time, testing infrastructure, documentation upkeep, and trained support staff who must remain familiar with each supported version. Without continued investment, it is not practical—or responsible—to offer open-ended support for legacy releases.
From a technical and operational perspective, unsupported versions quickly diverge from the modern ecosystem. Operating systems evolve, hardware changes, third-party libraries, including licensing systems for which we may have little or no control, are updated or deprecated, and security expectations increase. Maintaining the ability to diagnose and resolve issues in older versions would require us to freeze tooling, retain obsolete build environments, and continually re-validate fixes across multiple historical codebases. This level of ongoing investment is simply not sustainable without a mechanism that funds ongoing development and support. Consequently it is not even possible to guarantee that an older version of Gig Performer will run correctly on an operating system that was released after our product release although obviously we will always do our very best to ensure that versions of Gig Performer that are still fully supported will work on available OSs.
While we do not currently have an explicit maintenance or subscription-based support program, the upgrade fees charged for new major versions serve a similar purpose. Those fees help fund continued development, testing, and support for the actively maintained versions of the software. Customers who choose not to upgrade are not required to do so; however, once a version falls outside the defined support window, failures or issues encountered in that legacy version are not eligible for support, investigation, or fixes.
The one-year support period following a new major release provides a clear and reasonable transition window. It gives customers sufficient time to plan and execute upgrades while still having access to full support for their existing version. At the same time, it enables us to focus our resources on versions that are actively maintained and funded, ensuring higher quality, faster responses, and continued innovation for the user base as a whole.