A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

Hey team! I’d like to propose a *v1.2.0* minor release before we dive into the big wave of upcoming changes.
We’ve got some solid improvements ready to go (everything tested, including on full-sized datasets):
 • :jigsaw: *Template update (*<https://github.com/nf-core/riboseq/pull/111|#111>) – shout-out to <@UE6D8290F> for this!
 • :new: *New P-site identification and QC with riboWaltz* (<https://github.com/nf-core/riboseq/pull/113|#113>)
 • :bug: *Fixed workflow ordering bug in metromap &amp; docs confusion* (<https://github.com/nf-core/riboseq/pull/114|#109>, fixed in <https://github.com/nf-core/riboseq/pull/114|#114>) — to be merged into `dev` later today if there are no objections.

Thanks <@U0365M9DE9J> for reviewing:pray:!
changelog: <https://github.com/iraiosub/riboseq/blob/feat-tubemap/CHANGELOG.md|CHANGELOG.md>

Getting this release out means users get these improvements sooner, and it’ll be easier to track any issues that appear later. _(I also have projects and collaborators depending on these updates — a tagged release would make our work fully reproducible.)_
Thoughts on making a release by the end of next week at the latest with what we already have by then? :rocket:

Sounds OK! Heads-up that I'm on leave next week, and I think <@UE4L64T4G> is too, so the Ribo-TISH multiqc plugin might not make it through review before that.

it would be great to have that in already to be honest, maybe it could wait another day or two?

I hear you, it would definitely be nice to have it in soon. The only concern is that adding it after next week would require another full round of testing and inevitably delay the release.
For v1.2.0, I think it’s safer to stick with what’s already tested and ready to go. Since everything is prepared, I might try to finalise it this week already and ask for reviews. We can follow up quickly with a v1.3.0 once the MultiQC plugin is reviewed and ready, along with other updates. This also keeps the PRs smaller and more contained, which makes reviewing much easier.

Preparing a MultiQC release usually takes at least a day, so getting that done as well as the PR review + merge is a bit of a tall order given that I only have a few working hours left before I go away next week..

that makes sense! would everyone be ok that we go ahead with 1.2.0 with just the improvements already listed, and we keep Ribo-TISH as a later addition in a new minor release so nothing is rushed?