How do pipeline maintainers/devs hear determine th...
# random
a
How do pipeline maintainers/devs hear determine their version bumps when it comes to
nf-core
pipelines? e.g. with effectively “breaking” changes with regards to run-time things such as NF version, plugins/plugin versions, I could see justification for major version bumps, but given even a pipeline that pre-dates
nf-core
(sarek) is only on v3, it seems this isn’t the line of thought for others?
🤔 1
j
I consider breaking changes a change on how to run the pipeline 🤔 a silly example would be changing the parameter
--input
to
--input_file
👍 2
j
Meh it seems to vary. I have now moved to what Júlia described. If an old samplesheet or input option doesn't work then major bump
👍 1
Either that or matching each nextflow DSL 😬
e
It’s a vibe
😆 1