Agreed. This would make the most sense. Though, this could be what's actually in store. If indeed the core is modular, plus all of Bitwig's devices, etc., then patching is likely module-level as well. Further, these modules would have respective versions and license attributes.poonna wrote:I would say that the major concern for this scheme is that there's no bugfixes after the update period runs out.
I'm trying to see this from both sides of view. From the development point of view, it is also not technically feasible to keep backporting bugfixes to every previously released version to keep everyone happy.
I think a better way to handle this is:
Freeze the minor version released at the end of update period, but still allow for hotfixes for that minor version released after the end of the period.
For example: If at the end of my 12 months, I'm at version 2.3.2. I should still be entitled to get all the 2.3.x releases (supposedly all the hotfixes within that minor version) after that, but not 2.4.x.
This, I think, will at least eases some bugfix anxiety for propective upgraders.
Btw, as you know, Bitwig already has a "package Manager". The means to do all of this is already there.
The next thing we may see is 'Premium Devices'! ... Whatever may come, please don't turn Bitwig into an 'App Store'!
