My question here is if we should keep testing against EOL ROS releases, such as Indigo, that still uses OpenCV 2. I think that this raises extra work on maintainability and development, for example I will not be able to implement TApi codes implemented here that uses Opencv3, so this implementation will not work with OpenCV2.
My proposal is that we only run tests for non EOL distribution. Or, If you think that there is a need to keep the old distribution maintenance, I see that disable some features only available to newer versions would be a valid possibility, something more or less like here .
Hi all,
My question here is if we should keep testing against EOL ROS releases, such as Indigo, that still uses OpenCV 2. I think that this raises extra work on maintainability and development, for example I will not be able to implement TApi codes implemented here that uses Opencv3, so this implementation will not work with OpenCV2.
My proposal is that we only run tests for non EOL distribution. Or, If you think that there is a need to keep the old distribution maintenance, I see that disable some features only available to newer versions would be a valid possibility, something more or less like here .
What do you think @k-okada ?