COMP: set remote module to follow master

Follow the master branch for this remote module instead of a particular change set.

You can add the patch label if you want to merge without dashboard testing.

added patch label

There was extensive discussion about this in #1738 (closed) and we did not reach a conclusion. How do you plan on handling OTB releases?

My 3 remote modules don't change frequently. I would move OTB to follow their master branch and I would ensure from my side that this branch is stable for OTB. I still have to do this work for my other 2 modules. My rationale is that I expose master to OTB, develop for people who want to build setting the module to OFF in OTB's cmake and building the module otherwise, and feature branches for people working on the module itself.

Any comments? Anything blocking the merge? Thanks!

mentioned in commit aa574296

merged

changed milestone to %7.0.0

added packaging label

added refactoring label