Well, great, the only things, still missing, would be, to also get a v.3 Forum as well,
to 'handle' those, unable to get one of the older v.3 Subversions to work.
And then someone, able and willing to reply to the many Topics, where Users are
already seeking some assistance, Themes, and thousand other Gizmos ...
Ernie

Update 20.July, the V-3 Forum now exists !

For Sale: Top URL's, including an OpenCart V-Pro Shop!
A wide range of matching Designs can be seen here: http://www.opencart.li
For Information on URL's offered, please contact me at: jti@jacob.chHundreds of Mods in 380+ Repositories for OC v.1.5.x - v.2.3.x
to be found on my Github Site: https://github.com/IP-CAM

There's no need to wait for a new release while Github Opencart rather expects from us to download the package periodically which prevents on releasing new releases on a constant basis all-together.

The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.

So basically, go to github/opencart and
use the clone or download button, then just pull the latest zip file, then unzip it and ftp all the files over the latest released version which at this point if V3.0.2.0 on the server, then go to the /install folder and upgrade ? or am I missing something? How often do you suggest doing that ?

I disagree with straightlight. I strongly recommend NOT downloading the code from github for a live store --- it may have bugfixes and other improvements over the release versions, but (at least historically) it also often has unfinished code. That partially implemented code can cause major issues in some circumstances when trying to use it on a live installation.

My recommendation is to download an official version, and then apply the bugfixes that have been noted in the bugfix topic. If you find other bugs, post in that topic (or the appropriate support sub-forum) and see if anyone has a fix. I understand that's not ideal --- and what we'd all like is more frequent bugfix releases --- but in my experience that's the quickest way to a stable store.

If you do end up downloading from github and have a good experience with it, please post in here so others know that the current github revision (as of Dec. 17th, 2017) is stable and without any unfinished code.

I disagree with straightlight. I strongly recommend NOT downloading the code from github for a live store --- it may have bugfixes and other improvements over the release versions, but (at least historically) it also often has unfinished code. That partially implemented code can cause major issues in some circumstances when trying to use it on a live installation.

My recommendation is to download an official version, and then apply the bugfixes that have been noted in the bugfix topic. If you find other bugs, post in that topic (or the appropriate support sub-forum) and see if anyone has a fix. I understand that's not ideal --- and what we'd all like is more frequent bugfix releases --- but in my experience that's the quickest way to a stable store.

If you do end up downloading from github and have a good experience with it, please post in here so others know that the current github revision (as of Dec. 17th, 2017) is stable and without any unfinished code.

It is puzzling at this point. The Opencart forum focuses on the Bug Reports section due to passed encountered issues provided from the downloads section of opencart.com while even the Opencart creator rather focuses on the bug fixes from Opencart Github in order to constantly post reported issues along with added / removed features without any notifications than for each users to see the updated changes on Github. The same team all-together working on separate sides among several hundreds of thousands of users depending on this platform in order to obtain what they want.

The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.

I'd have to agree with Johnathan, yes there may be fixes in github, but likely a ton of other new issues possibly related to either new unfinished features, or new untested issues created by bug fixes. But it all depends on how strict they are with branch control. If we had some definite clarification that there is a dedicated 3.0.2 branch would ONLY have bug fixes checked in, then it might be ok, but I don't see a 3.0.2 branch.. only a 2.3, dev, and master.. of which I have no idea which is which.

This there are not that many releases per year and they are not automated, why not create a branch for the current release?
This would make it much easier for folks that are waiting for bug fixes on the current release.

I'd have to agree with Johnathan, yes there may be fixes in github, but likely a ton of other new issues possibly related to either new unfinished features, or new untested issues created by bug fixes. But it all depends on how strict they are with branch control. If we had some definite clarification that there is a dedicated 3.0.2 branch would ONLY have bug fixes checked in, then it might be ok, but I don't see a 3.0.2 branch.. only a 2.3, dev, and master.. of which I have no idea which is which.

The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.

Take note that, until official notice, the 3.0.3.0b release is not an official release.

The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.

Hello.
Thanks for the information. I googled a lot to find any kind of roadmap...maybe you can help me?!
Is there any site, where we can see the progress to the next, final release? Or an estimate?
I‘m about to set-up a new shop and I‘m wondering, if it is a matter of days, weeks or month.

No estimate. v3.0.2.0 release works well as it is when installing the bug fixes provided on the bug reports section of the forum. Very few codes to update afterwards but minor severity compared to previous versions.

The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.

No estimate. v3.0.2.0 release works well as it is when installing the bug fixes provided on the bug reports section of the forum. Very few codes to update afterwards but minor severity compared to previous versions.

Still I see many bugfixes on GitHub, I'm surprised there hasn't been a release, it's been quite a while now...

Hello,
we are about to upgrade our existing shop from Opencart 1.6 to the latest Opencart 3.
- I can see, that the latest offical release (3.0.2.0) is about one year old
- I recognized, that there is a beta 3.0.3.0b
- also there seem to be a Cloud-Edition upcoming

As I'm a newbee, I hope, that some of the OC-Veterans can help me to decide and answer some questions:
- Will the next release be ONLY for Cloud or will be a "classic" version also available in future?
- Do you guys think, that the next release will be within the next four weeks? Just an estimate...I know, that there is no guarantee ;-)
- Would you start with 3.0.3.0b or go for 3.0.2.0?
- If you recommend 3.0.2.0, how can I filter for "Hot Fixes" the best way