@Niels_Dekker thanks again for your contribution and your persistence!
Yes, we can do better in terms of making incremental improvements. If additional features could optionally be added in future commits, we should create an issue in the issue tracker and move forward.
At the same time, changes to improve regression test coverage, style changes, API changes, and similar should be made before the patch is merged, otherwise they may (likely) never happen.
Merging faster is also possible when follow-up’s come quickly for issues identified on the Nightly Dashboard builds. If these are not fixed quickly, they mask issues from other patches that other community members are trying to develop.
Currently, there are four issues causing warnings from the
ShapedImageNeighborhoodRange patch – I will take care of these, unless you get to them before me .
Boundary condition improvements sound excellent! We are targeting 5.0 Alpha 2 sometime over this week…