Release tracking

[antonylebechec]

Dear EtieM,

Would it be possible to track releases of OutLyzer?
Acutally, installation procedures (such as with Docker) failed if older release are not available.

Thanks a lot!

Best regards,

[EtieM]

Hello Antony,

I've just run a test to clone the repository and apparently it worked to download the last version (3.2). Let me know if you continue to have the issue

Etienne

[antonylebechec]

Hello!

I perfectly download the code, it's not the issue.
But the issue is when a installation script link a specific release (e.g. release 3.0 with file "outLyzer.py" downloaded in a Dockerfile) that is no longer available (e.g. now the script is "outLyzer_V3.2.py"). The installation/deployment script is broken...
It should be great to either:

• use git branch/tag to track each release of OutLyzer (easily downloadable with URL including branch/tag)
• keep script with release name (e.f. "outLyzer_V3.0.py", "outLyzer_V3.1.py", "outLyzer_V3.2.py"...)

Let me now if it is feasable.

BTW, OutLyzer is a great tool!

[EtieM]

Thanks for the advice and your feedback, good to hear! I'll apply the correction today (release in the script name).
And just for my curiosity (if you can answer), do you use it only for research purposes or in a clinical setting too?

[antonylebechec]

Thanks a lot for releases and tags!
We use OutLyzer for clinical analyses. It is a part of our pipelines (oncology and mosaicism).