I agree. I have a 1.5.4 fork on github just for bug fixes at https://github.com/opencarthelp/opencart_stable. Unfortunately I never had time to start 1.5.5 and the official bug fix fork seems to have been dead for quite a while now.JNeuhoff wrote:This has been an ongoing problem with the OpenCart project, it's all about managing the source code repositories. There are probably a number of bugfixes which have not been back-ported from Opencart 2.0 to 220.127.116.11. Qphoria used to do something like this in the past, e.g. with the 1.4.9.x series of OpenCart, but I doubt any of the 1.5.x.x releases are 100% bugfree. I used to maintain a number of my own bugfixes in the form of VQmod XML files in past OpenCart releases. It would be nice if each new OpenCart release could be supported with security and bug fixes for a guaranteed amount of time, just as is done with e.g. Ubuntu Linux releases.SelfMan wrote:What really bugs me is that this problem has already been fixed in march in github BUT the fix wasnt applied in the 18.104.22.168 branch. The code is too complex to hunt for such small bugfixes :-(
I think that the new 1.6.x version (or what ever it will be named) has so many enhancements, that it will be a very difficult upgrade process if you have customized modules.
(P.S.> sorry to be a bit off topic...)
There are a lot of talented developers in the community. Why not delegate out some of the low-level maintenance work to a group? The alternative is nothing being done at all.