Versioning Question for the nf-core/pacvar Release

Ask for help
1

The current release version of pacvar is 1.0.1 (first metro below). Since then, we have added six major modules to the pipeline (second metro belowO: hificnv (copy number variats), pbmerge (to merge fail bam), sawfish (structural varians), pbcpgtools (5mC methylation), ensemblvep (annotation), and fibertools (m6A/nucleosome processing). Together, these additions substantially expand the pipeline’s ability to support PacBio long-read sequencing analysis.

This represents a major update from 1.0.1. At the moment, the development version is still labeled 1.1.0.dev. Should we keep the next release version as 1.1.0, or would it be more appropriate to bump it to 2.0.0?

v.1.0.1

image
image1738×638 125 KB

v1.1.0dev
image
image1884×1026 225 KB

Thank you,
Chao-Jen Wong

2

Hi @chaochaowong , I think this is more a question to ask in the nf-core Slack since it’s so specific to nf-core.

3

Hi @chaochaowong,

Versioning of nf-core pipelines follows Semantic Versioning. You can check it at the nf-core page clicking here. Based solely on what you shared, I don’t see breaking changes, so I’d say it’s a minor release and I’d recommend going from 1.0.1 to 1.1.0.