@Jake Robinson Thanks a lot for your answer!

Your assumption is not totally right in our case because we use git to maintain our versions. There are no upgrades unless we update the embedded git repositories. Thus, it would not update the whole system. That's why we can (sometimes) use `./odoo-bin -u all` or `./odoo-bin --update=all` now if we work from code.

But logged in admins don't have this option in the frontend for `--update all`, right?

Furthermore, to simplify communication between developer/devops/logged-in admins - it would be nice to be able to update one module with its dependencies. So, there is no need to explicitly update every single dependency in the frontend when the logged-in admin has to do the install (who may be different from the programmer).

We also thought to parse the manifest file so we can use the depends as parameter for `--update` (no need for cascading updates), but this would also just work when working from code.

Hi Michael,

Any time you are making changes to a module that you depend on, you should always be updating that module. 

If upgrades also upgraded the modules that they depend on, nearly every time you upgrade a module it would upgrade every module in the system.

If this is causing you too many headaches keeping track of what you've updated, just run a base upgrade when you make changes. It may take a little longer but it will ensure you don't get this issue.

Cheer,
Jake Robinson