AstroVIPER and XRADIO will move to use a "develop" branch to merge their features and will use main only for main releases. This is in-line with the RADPS Test Strategy and we need to adapt testviper to follow that. This ticket is to discuss the design we want to implement for the workflow actions and the dependency mapping that we will need to use to build the components.
As a note, testviper Makefile already supports building the components with mixed dependencies, which can be achieved by calling:
make build-refs \
XRADIO=78-io-rework \
GRAPHVIPER=v0.3.1 \
ASTROVIPER=2c4b0f1 \
TOOLVIPER=main
For example, build xradio's zarr V3 branch and use the main branch of astroviper, graphviper and toolviper
make build-refs XRADIO=355-zarr-python-v3-and-zarr-v3
See the README.md of testviper.
AstroVIPER and XRADIO will move to use a "develop" branch to merge their features and will use main only for main releases. This is in-line with the RADPS Test Strategy and we need to adapt testviper to follow that. This ticket is to discuss the design we want to implement for the workflow actions and the dependency mapping that we will need to use to build the components.
As a note, testviper Makefile already supports building the components with mixed dependencies, which can be achieved by calling:
For example, build xradio's zarr V3 branch and use the main branch of astroviper, graphviper and toolviper
See the README.md of testviper.