Create tooling for automatic module version bump
We need some tooling to (semi-) automatically bump module version to the next version. This will hopefully take the burden of performing stupid tasks from maintainers. (Whether it actually can be used fully automatically depends on whether changes are reuired due to upstream changes.)
Idea:
- Regularly run a job checking whether a new major version of Tryton is released.
- If so, checkout each of the modules in trytoncommunity, bump the required Tryton version and run the tests.
- If tests pass, create a new branch (git) or topic (hg), push and create a merge request.
Complications:
- Modules can only be tested if its dependencies are available in vor the new Tryton version already.
This not only implies we need to bump packages in order, but also need some means of publishing ".dev" versions.
Fortunately heptapod/gitlab provided group package repositories and pip can be told to install ".dev" versions. - If additional changes are required to many packages, there is not much automation left.
Related ideas:
- Repos might opt-out from this service
- Repos might opt-in to auto-merge on success — rethink: only useful if only automatic changes are required.
- Opt-in/-out can be implemented by setting some kind of flag, e.g. add the project name to a file or set a CI/CD variable.
(A file might be a better idea since it can be version-tracked.)