Revision history [back]

E.g. OpenCV 4.4.0 and 4.4.0-openvino

E.g. It seems that CV_VERSION_STATUS could be ['-pre', '', '-openvino'], where -pre is for release candidate and '' is for a stable release.

OpenVINO is a toolkit or metapackage, one of Intel products for CV/ML.

If you look at the difference between OpenCV 4.4.0 and 4.4.0-openvino or the difference between 4.5.0 and 4.5.0-openvino you will notice, that opencv-openvino lacks a bunch of commits.

I do not think that OpenVINO package uses some sort of unstable OpenCV release, rather there are some important differences between them, there should be a reason, why Intel does that.

Please do not submit answers like 'L325 on file FILENAME.c, it's obvious!'. Yeah, it is obvious, that they have different amounts of commits.

I am asking for general patterns like 'opencv-openvino always misses ARM architecture' or 'it can't be used with widows', etc.

PS: I also asked that question on stackoverflow

It seems that CV_VERSION_STATUS could be ['-pre', '', '-openvino'], where -pre is for release candidate and '' is for a stable release.

OpenVINO is a toolkit or metapackage, one of Intel products for CV/ML.

If you look at the difference between OpenCV 4.4.0 and 4.4.0-openvino or the difference between 4.5.0 and 4.5.0-openvino you will notice, that opencv-openvino lacks a bunch of commits.

I do not think that OpenVINO package uses some sort of unstable OpenCV release, rather there are some important differences between them, there should be a reason, why Intel does that.

Please do not submit answers like 'L325 on file FILENAME.c, it's obvious!'. Yeah, it is obvious, that they have different amounts of commits.

I am asking for general patterns like 'opencv-openvino always misses ARM architecture' or 'it can't be used with widows', etc.

PS: I also asked that question on stackoverflow