Prepare release 2.7.1

[maxulysse]

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - add to the software_versions process and a regex to scrape_software_versions.py
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/sarek branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core lint .).
• Ensure the test suite passes (nextflow run . -profile test,docker).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[FriederikeHanssen]

Looks pretty good. I think some things ar emissing fom the Changelog. With regards to #378 Do you still want more tests before releasing?

[maxulysse]

Looks pretty good.

<3

I think some things are missing from the Changelog.

I did not pay attention to CHANGELOG lately, I'll make a PR for that.

With regards to #378 Do you still want more tests before releasing?

Yeah, but not specifically for #378 only I think @ggabernet was having issues (#380) which I think are now fixed in this version.

[FriederikeHanssen]

I tried launching the pipeline with tower on our cluster and the new launch interface. for the field Email I get:

[maxulysse]

I tried launching the pipeline with tower on our cluster and the new launch interface. for the field Email I get:

I have no issue on the command line with:

nextflow run . -profile docker,test --email me@me.com

Any idea @nf-core/core

[maxulysse]

Since this release is still DSL1, I wanted to put msisensor-pro in the main container, as it's usual to do.
But major Conda conflicts prevents me to do so.
So @nf-core/core @nf-core/sarek what do you think we should do?
Keep msisensor-pro in a separate container as we're doing now, and forget about about and go on more adventure with DSL2 ?

[jfnavarro]

Since this release is still DSL1, I wanted to put msisensor-pro in the main container, as it's usual to do.
But major Conda conflicts prevents me to do so.
So @nf-core/core @nf-core/sarek what do you think we should do?
Keep msisensor-pro in a separate container as we're doing now, and forget about about and go on more adventure with DSL2 ?

Doesn't seem like you have much of a choice, do you?

[maxulysse]

Doesn't seem like you have much of a choice, do you?

Yeah, it seems like so

[maxulysse]

@nf-core/sarek Can I get approvals so that I can release (I can do it today, tomorrow or Thursday, but not Friday ;-))

[FriederikeHanssen]

Looks good to me 🎉 , pending the CI tests passing

[jfnavarro]

They look good to me!