Would it be possible to publish a stable/versioned release of the pipeline, while continuing active development on the dev branch?
For reproducibility, it would be really helpful to have a fixed version/tag that users can reference. At the moment, relying on dev makes it difficult to ensure that analyses can be reproduced exactly in the future, since the code may change over time.
I completely understand the need to keep developing and adding features on dev; the suggestion would simply be to periodically cut a stable release from it and keep dev available for ongoing development.
This would make it much easier to use the pipeline in reproducible workflows while still allowing development to move forward.
Thanks a lot for considering this!
Would it be possible to publish a stable/versioned release of the pipeline, while continuing active development on the dev branch?
For reproducibility, it would be really helpful to have a fixed version/tag that users can reference. At the moment, relying on dev makes it difficult to ensure that analyses can be reproduced exactly in the future, since the code may change over time.
I completely understand the need to keep developing and adding features on dev; the suggestion would simply be to periodically cut a stable release from it and keep dev available for ongoing development.
This would make it much easier to use the pipeline in reproducible workflows while still allowing development to move forward.
Thanks a lot for considering this!