[Feature-Request] Merge features into release branch / add "Known issues"

Hello. I like the products, but I see in multiple issues/on discord/forum etc. to use this/that branch, for example multi_cam_support, there is an open PR for it, the first commit was made 11 month ago, according to github. I don’t specifically need it, I just picked as an example because it’s old and seems to be an important feature for many.

The other example is image_manip_refactor which seems to solve a lot of issues, but there isn’t a PR opened for it, so only from issue comments/discord it’s known that it exists.

What is the policy when it comes to features/releases?

Last but not least do you have a page/github issue with “Known issues” which can be tracked easily? For example the script node issues, or ImageManip issues etc.

[OanaMariaVatavu]

My suggestion is to merge image_manip_refactor at least when all the issues addressed(for the mainline version, and also for the refactor version) are resolved. If I should give an estimation, I would say 1 week just for that, but it’s not a guarantee because some of the issues are so heavy ones( like the stack overrides data/text section which implies random behavior). After all the issues addressed are resolved, I will start the permutations validation. So, for when the exhaustive validation will be done and the stability guarantee, I sincerely can’t estimate. @themarpe, @Erol444 if the “Known issues” section has been already added, please let me know, and I will document the ones related to the ImageManip node.

[jasonm189]

ImageManip got merged. WOW! Multi cam support next week?