Keeping 3.0.3.1 up to date
Posted: Fri Mar 29, 2019 7:11 pm
Coming back to OC after a long break (since 1.5 - it's nice to see so many old usernames still here
) and thinking about running the latest version (3.0.3.1) so have a couple of OC3 noob questions.
1. Is it safe to use 3.0.3.1 in production, or is there some older version or fork that everyone prefers (and maintains)?
Some of the issues I can see here and on github seem quite serious (e.g. https://github.com/opencart/opencart/is ... -459154982), but there is also a lot of noise from users that are just having trouble with mods/extensions that were written for older versions or that prefer vqmod to ocmod. Mod/extension compatibility isn't something that's going to bother me because I already know what I need to do for this project, and ocmod has been fine for me so far, the smaller featureset than vqmod makes sense given its more specific purpose. Are there solid reasons beyond mod/extension compatibility for not using 3.0.3.1 / using some other version instead?
2. How do I keep 3.0.3.1 (or everyone's preferred stable version) up to date?
Because it might be a long time before another version's released, and because that version might be dramatically different to 3.0.3.1, I want to keep 3.0.3.1 up to date with the latest bugfixes. Back in the days of 1.5, I used to maintain a vqmod of fixes. Now that the code's in github, I was hoping that I could use tags to cherrypick changes into a vqmod (which seems like the cleanest way to do it without leaning too heavily on git or hacking at ocmod), but the 3.0 maintenance tag seems like it might not catch everything. If there's a maintenance project then I'd be happy to contribute to it. It wouldn't even need to be a project that handled potentially big architectural changes, just something that dealt with typos, misplaced variables etc,.

1. Is it safe to use 3.0.3.1 in production, or is there some older version or fork that everyone prefers (and maintains)?
Some of the issues I can see here and on github seem quite serious (e.g. https://github.com/opencart/opencart/is ... -459154982), but there is also a lot of noise from users that are just having trouble with mods/extensions that were written for older versions or that prefer vqmod to ocmod. Mod/extension compatibility isn't something that's going to bother me because I already know what I need to do for this project, and ocmod has been fine for me so far, the smaller featureset than vqmod makes sense given its more specific purpose. Are there solid reasons beyond mod/extension compatibility for not using 3.0.3.1 / using some other version instead?
2. How do I keep 3.0.3.1 (or everyone's preferred stable version) up to date?
Because it might be a long time before another version's released, and because that version might be dramatically different to 3.0.3.1, I want to keep 3.0.3.1 up to date with the latest bugfixes. Back in the days of 1.5, I used to maintain a vqmod of fixes. Now that the code's in github, I was hoping that I could use tags to cherrypick changes into a vqmod (which seems like the cleanest way to do it without leaning too heavily on git or hacking at ocmod), but the 3.0 maintenance tag seems like it might not catch everything. If there's a maintenance project then I'd be happy to contribute to it. It wouldn't even need to be a project that handled potentially big architectural changes, just something that dealt with typos, misplaced variables etc,.