I feel, that will be less of a problem for FL Studio users, with our Lifetime Free Updates, than it would be for other DAWs which usually make users pay for their "major" updates.NFX wrote: ↑Sat Mar 30, 2024 7:38 pmConsidering FL 20 existed from 2019 to late 2022 becuase there were not enough MAJOR changes, I feel using the year this may be a mistake.
Primarily because people will assume each year the MAJOR version number will change and with it should come actual MAJOR changes as you stated "what year is it?"
What if they don't change the version number and we are using FL 2024.x in 2026? I think people will be confused and disappointed.
As a person who maintains previous FL versions, it could get quite storage heavy after a few years if the MAJOR version changes each year and requires a new folder and data upon installation.
But (unless I'm wrong), I don't believe the yearly number change need necessarily coincide with any "major" changes. Perhaps some year, a minor "bug fix" happens to fall in late January 2026, for example. And so that update, being the first to come out in that year, just so happens to be the first release with the updated year FL Studio 26?
After a while, I believe FL Studio customers will learn that 'major' changes can come about at ANY time, and not just because of or coinciding with a new year, when the first update of the DAW bears the name change. But we'll see.
Either way, such updates are remaining free, (Lifetime) right? ...
