Page 1 of 1

Keeping 3.0.3.1 up to date

Posted: Fri Mar 29, 2019 7:11 pm
by ogun
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,.

Re: Keeping 3.0.3.1 up to date

Posted: Fri Mar 29, 2019 9:13 pm
by IP_CAM
How do I keep 3.0.3.1 (or everyone's preferred stable version) up to date?
Well, better don't count on anybody else. There is not preferred stable Version so far, at
least not, when it comes to OC-3. And if you come back in 4 Years again ( as you seemengly
did now ), nobody will even remember v.3.0.3.1 anymore, that's for sure. :laugh:

But you should know, after beeing around for such a long time, OC is an ongoing project,
and only a few People feel like sharing their knowledge with others, in an environment,
where it's all about Competition. OC is no longer, what it used to be, a good while ago,
and most leave the Scene again, like you, after getting, what they are looking for.

So better accept it, as it comes, the World is getting more competitive, day by day, and
this just has to be accepted, as a Fact. ;)

Good Luck!
Ernie

Re: Keeping 3.0.3.1 up to date

Posted: Mon Apr 01, 2019 8:55 am
by ogun
most leave the Scene again, like you, after getting, what they are looking for.
I wish that had been the reason, it was more one of life getting in the way :)

It seems like I'll be able to find most stuff by comparing 3.0.3.1 to maintenance, but not everything. For example, it doesn't have this (which is a bug on 3.0.x.x_Maintenance as well as master). I need to learn about branches and pull requests. Have been trying to avoid learning git for as long as possible because it feels like a command line adventure game for masochistic neckbeards :(

Re: Keeping 3.0.3.1 up to date

Posted: Mon Apr 01, 2019 9:23 am
by IP_CAM
it feels like a command line adventure game for masochistic neckbeards
Well, I feel with you, especially, since the most modern way of communicating with Github
is not available for my beloved XP, and I would have to go back to the early 90's, by use of
a DOS Window, as well as using 2 different Progs, just to get my Work up 'in Github Place'.
Good Luck!
Ernie