Rethink WMS and CTADIRAC repository coupling
Looking at the coverage of CTADIRAC, it seems to me that getting a meaningful amount of coverage in the CTADIRAC project would require running integration tests with a running DIRAC instance that is using the current development version of CTADIRAC both server- and client side.
This for me means, we should probably rethink the coupling between the two repositories.
Maybe we should just add the configurations here to the CTADIRAC repository, rename it to WMS and use the CTADIRAC versioning for WMS (i.e. the next WMS release would already be 2.2.X) and the python package would keep the CTADIRAC name.
Having a single repository would allow us to:
- build DIRAC server/ce/client images with the current dev version of CTADIRAC
- run integration tests in these with a live DIRAC instance
- Have earlier failures in case something in DIRAC brakes CTADIRAC or vice versa.
Let me know what you think @arrabito @natthan.pigoux