debops install methods, updates and rolling release

Hi to all, today, after installing debops via the debops.debops role on an remote ansible controller I realized that I was always confused about the debops mono repo with rolling release vs the pip install command. What I (hopefully) understood: * when installing debops via pip everything is under ./local/lib/python3.7/dist-packages * after debops-update there will be an additional debops repo in ./local/share/debops/debops/ The latter is on git branch master - while the repo from pip is on the release tag - but once I have an repo in local/share/debops it will have precedence over the first according to file path order in .debops.cfg. Right? What I did all the time working with debops, was ignoring the pip installation and used git pull && git checkout <Release-Tag> to update my debops to an stable release. Now I realized that the debops.debops role always automatically cloned the monorepo to /usr/local/share/debops/debops - in the master branch. No I wondering: * is it a good practice at all just to use git checkout inside the monorepo - what I did all the years to get an specific release? * does the debops.debops role always lead to an debops version on branch master or is there an possibility to configure an release? And one last question: what purpose has the [debops_recursively] host group? Thanks and kind regards Jan