After the release of VM4.4.4, a minor update with major concequenses, I've been thinking.
Should VirtueMart follow Joomla's release schedule?
Would it prevent the isImage bug? Perhaps not. But it would prevent it from happening in a security update.
Minor Z updates: every 6 weeks, bugfixes
Major Y updates: every 6 months, bugfixes & new features
New X version: every 24 months, bugfixes, new features & BC breaks
VM : Release Date (J. Released) - VM support
4.4.6 : ASAP/18 Feb 2025 (J4.4.x/J5.2.4) - J3/4/5
4.4.8 : 1 April 2025 (J4.4.x/J5.2.5)
4.6.0 : 15 April 2025 (J4.4.x/J5.3.0)
4.6.2 : 27 May 2025 (J4.4.x/J5.3.1)
4.6.4 : 8 July 2025 (J4.4.x/J5.3.2)
4.6.6 : 19 August 2025 (J4.4.x/J5.3.3)
4.8.0 : 14 October 2025 (J4.4.x/J5.4.0)
5.0.0 : 14 October 2025 (J5.4.0/J6.0.0) - J5/6
5.0.1 : 25 November 2025 (J5.4.1/J6.0.1)
5.0.2 : 6 January 2026 (J5.4.2/J6.0.2)
5.0.3 : 17 Febuary 2026 (J5.4.3/J6.0.3)
5.0.4 : 31 March 2026 (J5.4.4/J6.0.4)
5.1.0 : 14 April 2026 (J5.4.x/J6.1)
(...)
5.2.0 : 13 October 2026 (J5.4.x/J6.2)
(...)
5.3.0 : 13 April 2027 (J5.4/J6.3)
(...)
5.4.0 : 19 October 2027 (J5.4/J6.4)
6.0.0 : 19 October 2027 (J6.4/J7.0) - J6/7
7.0.0 : 16 October 2029 (J7.4/J8.0) - J7/8
8.0.0 : 14 October 2031 (J8.4/J9.0) - J8/9
I understand that no release schedule is perfect.
The beauty of the Joomla release schedule, I find, is that it's at regular interval and you can plan fixes and updates around it.
I know they are also working on VM for WP, but WP does not really have a release schedule (AFAIK).